unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Lars Ingebrigtsen" <larsi@gnus.org>,
	"Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 45125@debbugs.gnu.org
Subject: bug#45125: Subject: 28.0.50; defvar dynamics
Date: Tue, 8 Dec 2020 13:54:15 -0800 (PST)	[thread overview]
Message-ID: <f4e22dd8-4604-4401-b704-e0fd4225726e@default> (raw)
In-Reply-To: <87o8j49haq.fsf@gnus.org>

> See NEWS:
> 
> ** 'eval-last-sexp' now handles 'defvar'/'defcustom'/'defface'
> specially.
> This command would previously not redefine values defined by these
> forms, but this command has now been changed to work more like
> 'eval-defun', and reset the values as specified.

Yes, well, this does mean that you can no longer realize
the old behavior.

It's good to be able to interactively evaluate an
individual defvar, to have updated text take effect.

But by putting this on `C-x C-e' it means that you can no
longer select a whole bunch of code that might include
some defvars, and be able to count on the defvars having
their normal behavior (eval only when not yet initialized).

It might be good to have some way of getting the best of
both worlds.  Unfortunately, prefix args of various sorts
are already defined, and there's no easy way to have a
prefix arg that's orthogonal (i.e., can apply across the
other prefix-arg behaviors).

Of course, we still have `eval-region'.  Still, there's a
loss here, even if there's some gain.

IIRC, the main motivation for this change was the repeated
complaint that `C-M-x' doesn't update a `defface'.  How we
ended up with a wholesale change of `C-x C-e', including
for `defvar', I'm not certain.  Seems a bit of a shame, no?





  reply	other threads:[~2020-12-08 21:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 19:46 bug#45125: Subject: 28.0.50; defvar dynamics Andreas Röhler
2020-12-08 20:25 ` Lars Ingebrigtsen
2020-12-08 21:54   ` Drew Adams [this message]
2020-12-09  7:34     ` Andreas Röhler
2020-12-09 12:56       ` Lars Ingebrigtsen
2020-12-09 19:03         ` Andreas Röhler
2020-12-09 19:17           ` Lars Ingebrigtsen
2020-12-09 19:55             ` Drew Adams

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=f4e22dd8-4604-4401-b704-e0fd4225726e@default \
    --to=drew.adams@oracle.com \
    --cc=45125@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=larsi@gnus.org \
    /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).