GNU bug report logs - #493
describe-variable to keep track of where vars were set; not just where they were defined

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Glenn Morris <rgm <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#493: closed (describe-variable to keep track of where vars
 were set; not just where they were defined)
Date: Wed, 22 Feb 2012 01:06:02 +0000

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

Your message dated Tue, 21 Feb 2012 20:03:37 -0500
with message-id <eb8vjv4r2u.fsf <at> fencepost.gnu.org>
and subject line Re: bug#493: describe-variable misleading origin
has caused the debbugs.gnu.org bug report #493,
regarding describe-variable to keep track of where vars were set; not just where they were defined
to be marked as done.

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


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

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

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: describe-variable vs. not necessarily soul origins
Date: Sat, 28 Jun 2008 00:03:01 +0800

describe-variable shows e.g.,

  kill-emacs-hook is a variable defined in `C source code'.
  Its value is
  (w3m-arrived-shutdown
   (lambda nil
     (sleep-for 5))
   #[nil "\300\301!\207"
         [server-mode -1]
         2])

The problems are: Saying

  kill-emacs-hook is a variable defined in `C source code'.
  Its value is

is misleading, as it looks like you are saying "this is the definition
as found in the C source code" when in fact it has been modified
since.

So maybe say
  Its CURRENT value is

Or if you keep track of whether it has been modified or not, than say
two different things accordingly.

P.S., saying
   #[nil "\300\301!\207"
         [server-mode -1]
         2])
presents the user with unexplained octal gobbledygook.

And maybe even add a list of all the files that altered the variable,
so one can track down just what put that byte-compiled stuff there
(that one doesn't see with emacs -Q).

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

From: Glenn Morris <rgm <at> gnu.org>
To: 493-done <at> debbugs.gnu.org
Subject: Re: bug#493: describe-variable misleading origin
Date: Tue, 21 Feb 2012 20:03:37 -0500

I see no prospect of something like this being implemented.
Closed as wontfix.

Previous Next

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