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: Philipp Stephani <p.stephani2@gmail.com>,
	26624@debbugs.gnu.org,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#26624: 26.0.50; Generalized variable `buffer-local-value' does't restore local flag
Date: Tue, 23 Aug 2022 12:28:47 +0200	[thread overview]
Message-ID: <877d2ztfs0.fsf@gnus.org> (raw)
In-Reply-To: <87bksc0xa5.fsf@web.de> (Michael Heerdegen's message of "Mon, 22 Aug 2022 23:43:30 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

>> :variable (electric-indent-mode .
>>            (lambda (val) (setq-local electric-indent-mode val)))
>
> Looks good - similar specs are already used in other places.

Now pushed to Emacs 29 (and I've made buffer-local-value obsolete again
as a generalized variable).

> BTW: I find the definition of `electric-indent-local-mode' inelegant:
> the handling of the variable is split between the :variable spec and the
> body.  The body enables the global mode and sets the global variable
> back to nil - quite hackish.

Yes, it's not ideal at all.

> Anyway, if this is needed in more places it cries for a
> `define-localized-mode'.

I hope it's not used a lot -- we'd rather have modes work in the
opposite direction.  That is, the mode is local, and then we have
globalized versions of it.





  reply	other threads:[~2022-08-23 10:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 17:13 bug#26624: 26.0.50; Generalized variable `buffer-local-value' does't restore local flag Philipp Stephani
2017-06-17 13:10 ` Philipp Stephani
2017-06-17 18:48   ` npostavs
2017-06-18  4:17   ` Michael Heerdegen
2017-07-02 16:53     ` Philipp Stephani
2017-09-24 15:19       ` Philipp Stephani
2017-09-24 15:36         ` Michael Heerdegen
2017-09-24 15:44         ` Noam Postavsky
2017-09-24 16:42           ` Philipp Stephani
2017-09-24 17:43             ` Noam Postavsky
2017-09-29  7:50               ` Eli Zaretskii
2017-09-29 20:55                 ` Philipp Stephani
2017-09-30  6:46                   ` Eli Zaretskii
2017-12-26 22:19                     ` Michael Heerdegen
2017-12-27 16:10                       ` Eli Zaretskii
2017-12-27 19:54                         ` Michael Heerdegen
2017-12-27 20:27                           ` Eli Zaretskii
2017-12-29 14:08                             ` Michael Heerdegen
2017-12-29 16:14                               ` Eli Zaretskii
2017-12-29 16:20                                 ` Philipp Stephani
2022-08-21 21:38           ` Lars Ingebrigtsen
2022-08-21 22:21             ` Lars Ingebrigtsen
2022-08-22  6:53               ` Michael Heerdegen
2022-08-22 10:10                 ` Lars Ingebrigtsen
2022-08-22 21:43                   ` Michael Heerdegen
2022-08-23 10:28                     ` Lars Ingebrigtsen [this message]
2018-01-24 14:33       ` Michael Heerdegen
2018-02-04 19:01         ` Philipp Stephani
2018-02-04 21:02           ` Michael Heerdegen
2018-02-11 17:54             ` Philipp Stephani
2018-02-11 20:56               ` Michael Heerdegen

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=877d2ztfs0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=26624@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=npostavs@users.sourceforge.net \
    --cc=p.stephani2@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).