From: uzibalqa via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Heime <heimeborgia@protonmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: RE: [External] : Definition of a sexp
Date: Thu, 09 Jan 2025 23:06:32 +0000 [thread overview]
Message-ID: <fT8wOppszehTnhAnxPg7tt5s3nTDv7Mu_kzwpka2pMB5vIex8bDqkP8BhlqbDTDyTpGVIVtLuUL0hkiijIZX_mgESHAAZ0_Ta4vBcqzs0Xg=@proton.me> (raw)
In-Reply-To: <DS7PR10MB5232E996DD9DF659633CA209F3122@DS7PR10MB5232.namprd10.prod.outlook.com>
On Thursday, January 9th, 2025 at 11:54 AM, Drew Adams <drew.adams@oracle.com> wrote:
> > Can one then state that a sexp is either a balanced parenthetical
> > grouping, a string, or a symbol, that is subject to evaluation?
>
>
> I already told you what a sexp is, and why "basically"
> is used there - it just means there that those are
> important kinds of sexps.
>
> IOW, that's not an exhaustive list. It might have added
> "a number" and "a vector" to the list, as other important
> kinds of atom.
Right. "Not an exhaustive list" is much more informative and precise
that "basically". Some difficulties in the docs is that
> What "basically" does NOT mean there is that there are
> lists, strings, or symbols that aren't sexps. Of course
> you can pick nits such as representations of lists,
> strings, and symbols within comments or inside strings,...
>
> A sexp is a cons or an atom. That's the whole story.
> Read the rest of what I wrote or pointed you to, if you
> want details.
Good
prev parent reply other threads:[~2025-01-09 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 19:30 Definition of a sexp Heime via Users list for the GNU Emacs text editor
2025-01-08 21:12 ` [External] : " Drew Adams
2025-01-08 22:04 ` Heime via Users list for the GNU Emacs text editor
2025-01-08 23:54 ` Drew Adams
2025-01-09 23:06 ` uzibalqa via Users list for the GNU Emacs text editor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fT8wOppszehTnhAnxPg7tt5s3nTDv7Mu_kzwpka2pMB5vIex8bDqkP8BhlqbDTDyTpGVIVtLuUL0hkiijIZX_mgESHAAZ0_Ta4vBcqzs0Xg=@proton.me' \
--to=help-gnu-emacs@gnu.org \
--cc=drew.adams@oracle.com \
--cc=heimeborgia@protonmail.com \
--cc=uzibalqa@proton.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.