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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#19608: closed (25.0.50; Elisp manual: add index entry for
 major modes killing local variables)
Date: Thu, 15 Jan 2015 17:34:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 15 Jan 2015 19:33:07 +0200
with message-id <83r3uw2bl8.fsf <at> gnu.org>
and subject line Re: bug#19608: 25.0.50; Elisp manual: add index entry for major modes killing local variables
has caused the debbugs.gnu.org bug report #19608,
regarding 25.0.50; Elisp manual: add index entry for major modes killing local variables
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
19608: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19608
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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'

[Message part 3 (message/rfc822, inline)]

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.

Previous Next

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