From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Alan Mackenzie <acm@muc.de>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 19217@debbugs.gnu.org
Subject: bug#19217: 25.0.50; `C-M-x' (`eval-defun') on a `defface' that is not top-level
Date: Thu, 15 Oct 2020 08:29:46 -0700 (PDT) [thread overview]
Message-ID: <8439256f-09d7-4939-aef0-8d9d14d8e73c@default> (raw)
In-Reply-To: <87r1pzwokd.fsf@gnus.org>
> > To recap, this allows `C-x C-e' on defvar/defface to work the same as
> > `C-M-x' on those (when they are top-level).
> >
> > That these two work differently is a source of frustration, so I think
> > it makes conceptual sense, but I'm not sure what the repercussions would
> > be otherwise...
>
> There were no protests, so I've now gone ahead and done this. This may
> perhaps be controversial, but I've never understood why `C-x C-e'
> shouldn't do "the obvious thing" on defvar (etc) forms, so I've done it
> anyway.
>
> However, if this somehow gets in the way of people's way of working, it
> could be reversed, I guess.
Thanks for doing this.
But did you also fix `pp-eval-last-sexp'?
You said this:
> Saturday, September 19, 2020 7:11 AM
> > What about `pp-eval-last-sexp'?
> > Could we get that updated similarly?
>
> Sure, if we decide to alter `eval-last-sexp' in this way.
next prev parent reply other threads:[~2020-10-15 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<mailman.14952.1417284925.1147.bug-gnu-emacs@gnu.org>
[not found] ` <<20141129191023.34112.qmail@mail.muc.de>
2014-11-29 20:08 ` bug#19217: 25.0.50; `C-M-x' (`eval-defun') on a `defface' that is not top-level Drew Adams
2014-11-30 19:58 ` Alan Mackenzie
2014-11-30 20:51 ` Drew Adams
2014-11-30 23:20 ` Alan Mackenzie
2014-12-01 0:00 ` Drew Adams
2014-12-06 19:10 ` Alan Mackenzie
2014-12-10 22:20 ` Drew Adams
2014-12-13 3:07 ` Drew Adams
2020-09-18 13:36 ` Lars Ingebrigtsen
2020-09-18 15:53 ` Drew Adams
2020-09-19 14:10 ` Lars Ingebrigtsen
2020-10-15 14:28 ` Lars Ingebrigtsen
2020-10-15 15:29 ` Drew Adams [this message]
2020-10-15 15:35 ` Lars Ingebrigtsen
2020-10-15 16:15 ` Drew Adams
2014-11-29 18:13 Drew Adams
[not found] ` <mailman.14952.1417284925.1147.bug-gnu-emacs@gnu.org>
2014-11-29 19:10 ` Alan Mackenzie
2014-12-01 3:51 ` Stefan Monnier
2014-12-01 4:29 ` Drew Adams
2014-12-01 13:49 ` Stefan Monnier
[not found] ` <mailman.15037.1417408221.1147.bug-gnu-emacs@gnu.org>
2014-12-01 17:02 ` Alan Mackenzie
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=8439256f-09d7-4939-aef0-8d9d14d8e73c@default \
--to=drew.adams@oracle.com \
--cc=19217@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
/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).