From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32064@debbugs.gnu.org
Subject: bug#32064: 26; doc string of `eval-last-sexp'
Date: Fri, 06 Jul 2018 12:39:18 +0300 [thread overview]
Message-ID: <83va9sln3t.fsf@gnu.org> (raw)
In-Reply-To: <87bmbldxg3.fsf@gmail.com> (message from Noam Postavsky on Thu, 05 Jul 2018 20:23:08 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Thu, 05 Jul 2018 20:23:08 -0400
> Cc: 32064@debbugs.gnu.org
>
> Drew Adams <drew.adams@oracle.com> writes:
>
> > This is all a confusing mess, I'm afraid. And the code (e.g. of
> > `eval-last-sexp' and its helper `elisp--eval-last-sexp') is not very
> > clear either.
>
> I agree. I think the solution is to simplify the interface somewhat.
These additional features weer added just recently, so I see no reason
why we should remove them now. Certainly not because the doc string
needs to be fixed.
> As it stands, we're trying to cram a lot of functionality into the
> prefix argument, and the encoding is too difficult to remember (both in
> terms of implementing & documenting, as well as for using).
I had no difficulty bringing the doc string in line with the
implementation, please take a look.
next prev parent reply other threads:[~2018-07-06 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 20:15 bug#32064: 26; doc string of `eval-last-sexp' Drew Adams
2018-07-05 21:56 ` Drew Adams
2018-07-06 0:23 ` Noam Postavsky
2018-07-06 9:39 ` Eli Zaretskii [this message]
2018-07-06 11:47 ` Noam Postavsky
2018-07-06 17:55 ` Drew Adams
2018-07-06 9:37 ` Eli Zaretskii
2018-07-06 9:34 ` Eli Zaretskii
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=83va9sln3t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32064@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/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).