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

Previous Next

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

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

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

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 #10 received at 493 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: 493 <at> debbugs.gnu.org
Subject: describe-variable misleading origin
Date: Thu, 04 Feb 2010 02:53:52 +0800

(describe-variable (quote message-mode-hook)) gives
    message-mode-hook is a variable defined in `message.el'.
    Its value is
    (#[nil "\300\301\302\"\207"
           [local-set-key "^Ci" ispell-message]
           3])

      This variable is potentially risky when used as a file local variable.

    Documentation:
    Hook run in message mode buffers.

    You can customize this variable.

It looks to the user like that byte code is coming from message.el.
Actually it is coming from http://jidanni.org/comp/configuration/.emacs
(.emacs.elc), loaded before message.el. So maybe that origin should be
mentioned too.

You must admit "is a variable defined in `message.el'" is wrong.
It is defined in .emacs.elc. In message.el there is merely a empty defcustom.
emacs-version "23.1.92.1"

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

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.