unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 10495@debbugs.gnu.org
Subject: bug#10495: 24.0.92; pp-eval-last-sexp doesn't work on a `symbol' in quotes
Date: Wed, 20 Jan 2021 18:47:07 +0100	[thread overview]
Message-ID: <87im7rmrfo.fsf@gnus.org> (raw)
In-Reply-To: <87k44v8mip.fsf@web.de> (Michael Heerdegen's message of "Fri, 13 Jan 2012 19:50:38 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> the command `eval-last-sexp' has a very useful feature: Having point at
> a symbol (or a sexp) that is enclosed in `...'  (think of the manual or
> docstrings), the sorrounded quotes are ignored so that evaluation of it
> works.
>
> OTOH, `pp-eval-last-sexp' doesn't have this feature.  I think it really
> really should, I can't see any disadvantage.

Makes sense to me -- you don't happen to have a patch for this?  :-)

> Besides: IMHO it's a pity that pp.el is not described in any manual (or
> is it? - didn't find something).
>
> At least, the header of pp.el should describe how to use it.  E.g. just
> tell the user to do
>
>      (global-set-key [?\C-x ?\C-e] 'pp-eval-last-sexp)
>      (global-set-key [?\M-:] 'pp-eval-expression)
>
> or something like that.

Are there any cases where using the pp version of eval-last-sexp (etc)
would be awkward?  If not, adding a comment like that (and mentioning
the pp commands in the manual) sounds like a good idea.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-01-20 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 18:50 bug#10495: 24.0.92; pp-eval-last-sexp doesn't work on a `symbol' in quotes Michael Heerdegen
2021-01-20 17:47 ` Lars Ingebrigtsen [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=87im7rmrfo.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10495@debbugs.gnu.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).