From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 24386@debbugs.gnu.org
Subject: bug#24386: 24.5; `read--expression' --> `read-expression', please
Date: Sat, 27 Jul 2019 17:34:58 -0700 (PDT) [thread overview]
Message-ID: <1bee99ad-1bdd-4604-ab02-ce0a1b701bce@default> (raw)
In-Reply-To: <87r26bdrnb.fsf@web.de>
> > > > Please consider renaming `read--expression' to `read-expression'
> and
> > > > taking away its "internal" designation. What it does is equally
> > > > useful to ordinary Emacs user-programmers.
> > >
> > > It does seem like a rather internal function (setting up eldoc
> stuff
> > > and the like), so I think it's probably well-named as is; closing.
> >
> > There's _absolutely nothing_ internal about the
> > behavior this function offers. You can use it
> > _any_ place where you want to read a sexp.
>
> IMO we should offer an official way to read expression input. That
> would likely look very much like read--expression.
>
> > As for it using `eldoc-mode': That presumably makes the function more
> > useful for specifically Lisp-sexp reading. If we think otherwise
> > then that could be removed or optional.
>
> FWIW it wasn't there from the beginning - it was added while fixing
> Bug#27202. If we speak of Lisp, the name "expression" implies
> something to be intended for evaluation, so having eldoc support
> is totally legitimate.
>
> Why not also add a `read-sexp'?
+1 to all you said.
`read--expression' is a good beginning for such
a function. If we don't do as you suggest then it
would also be a good end: just remove the extra `-'.
(But I don't think the name "expression" implies
something to be intended for evaluation. It often
means that, but it's also used just for "sexp".)
prev parent reply other threads:[~2019-07-28 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 2:37 bug#24386: 24.5; `read--expression' --> `read-expression', please Drew Adams
2019-07-27 14:45 ` Lars Ingebrigtsen
2019-07-27 16:39 ` Drew Adams
2019-07-27 22:44 ` Michael Heerdegen
2019-07-28 0:34 ` Drew Adams [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1bee99ad-1bdd-4604-ab02-ce0a1b701bce@default \
--to=drew.adams@oracle.com \
--cc=24386@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).