From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: p.stephani2@gmail.com, 26624@debbugs.gnu.org,
npostavs@users.sourceforge.net
Subject: bug#26624: 26.0.50; Generalized variable `buffer-local-value' does't restore local flag
Date: Wed, 27 Dec 2017 18:10:49 +0200 [thread overview]
Message-ID: <83po70gnhy.fsf@gnu.org> (raw)
In-Reply-To: <871sjhcetm.fsf@web.de> (message from Michael Heerdegen on Tue, 26 Dec 2017 23:19:33 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Philipp Stephani <p.stephani2@gmail.com>, 26624@debbugs.gnu.org, npostavs@users.sourceforge.net
> Date: Tue, 26 Dec 2017 23:19:33 +0100
>
> I guess it's not really worth the time to implement an infrastructure
> for gv-expander obsoletion, because we will probably make use of it only
> every 150 years (estimation). So it could be that nobody wants to do
> this for quite a while.
>
> Would it be acceptable if the gv setter of `buffer-local-value' would
> just print a warning (i.e., solve it "by hand")? Not perfect, admitted,
> but still much better than leaving this unfixed.
Is it (better than leaving this unfixed)?
In any case, I don't think I understand the suggestion in detail. Can
you show a patch or an idea of a patch?
Thanks.
next prev parent reply other threads:[~2017-12-27 16:10 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 [this message]
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
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=83po70gnhy.fsf@gnu.org \
--to=eliz@gnu.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).