GNU bug report logs - #19608
25.0.50; Elisp manual: add index entry for major modes killing local variables

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Thu, 15 Jan 2015 16:57:02 UTC

Severity: normal

Found in version 25.0.50

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

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 19608 in the body.
You can then email your comments to 19608 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#19608; Package emacs. (Thu, 15 Jan 2015 16:57:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Drew Adams <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Thu, 15 Jan 2015 16:57:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.50; Elisp manual: add index entry for major modes killing local
 variables
Date: Thu, 15 Jan 2015 08:56:01 -0800 (PST)
I've seen a few times now the question posed as to why local variables
that have been set become unset.  Users who asked sometimes looked for
info in the Elisp manual but didn't find it.

Please consider adding an index entry that might help users get there
when looking up local variable information.  Dunno what the best such
entry/entries might be.  Perhap something like:

"local variables, killed automatically" or "local variables, killed by
major modes".  Anyway, you get the idea.

Here is one such question: http://emacs.stackexchange.com/q/7391/105.

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 rgm <at> gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'




Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Thu, 15 Jan 2015 17:34:02 GMT) Full text and rfc822 format available.

Notification sent to Drew Adams <drew.adams <at> oracle.com>:
bug acknowledged by developer. (Thu, 15 Jan 2015 17:34:02 GMT) Full text and rfc822 format available.

Message #10 received at 19608-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 19608-done <at> debbugs.gnu.org
Subject: Re: bug#19608: 25.0.50;
 Elisp manual: add index entry for major modes killing local variables
Date: Thu, 15 Jan 2015 19:33:07 +0200
> Date: Thu, 15 Jan 2015 08:56:01 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> I've seen a few times now the question posed as to why local variables
> that have been set become unset.  Users who asked sometimes looked for
> info in the Elisp manual but didn't find it.
> 
> Please consider adding an index entry that might help users get there
> when looking up local variable information.  Dunno what the best such
> entry/entries might be.  Perhap something like:
> 
> "local variables, killed automatically" or "local variables, killed by
> major modes".  Anyway, you get the idea.

Done.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 13 Feb 2015 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 10 years and 131 days ago.

Previous Next


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