GNU bug report logs - #26624
26.0.50; Generalized variable `buffer-local-value' does't restore local flag

Previous Next

Full log

View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Philipp Stephani <p.stephani2 <at> gmail.com>, 26624 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: bug#26624: 26.0.50; Generalized variable `buffer-local-value' does't restore local flag
Date: Tue, 26 Dec 2017 23:19:33 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> >  I agree. Removing some feature without due warning is not something
> >  we should do, except in very rare cases (which this one isn't).
> > 
> > I fully agree, but I don't know how to correctly deprecate a
> > generalized variable. Should I add code to the byte
> > compiler to deal with this case explicitly? 
>
> If no other idea comes up, yes, I think so.

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.


Thanks,

Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.