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

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"

Previous Next

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