bug#35628: Keep track of what file sets variables... through init-file processing

bug#35628: Keep track of what file sets variables... through init-file processing

[積丹尼 Dan Jacobson]

C-h v runs the command describe-variable.

Its output looks like

   ............. is a variable defined in ‘.......el’.
   Its value is t
   Original value was nil

So describe-variable knows several things including
- the original value of a variable.
- the file where that value was set.

- the current value of a variable.
- the file where that value was set <---- ALAS... it would know that
but that part of its record keeping quits before ~/.emacs is processed!

Try this: put (setq xxxx 2222) in ~/.emacs; restart emacs, and do
describe-variable xxxx.

You might say "Well we only remember one filename. If we remember
.emacs, then we will forget the original file."

Then I would say "You remember two values, then you should remember two files."

P.S., this has nothing to do with
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910021

bug#35628: Keep track of what file sets variables... through init-file processing

[Noam Postavsky]

forcemerge 29495 35628
quit

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> C-h v runs the command describe-variable.
>
> Its output looks like
>
>    ............. is a variable defined in ‘.......el’.
>    Its value is t
>    Original value was nil

> Try this: put (setq xxxx 2222) in ~/.emacs; restart emacs, and do
> describe-variable xxxx.
>
> You might say "Well we only remember one filename. If we remember
> .emacs, then we will forget the original file."

Only defvar, defcustom, or defconst record a variable definition
filename; setq records nothing (technically, it doesn't "define" a
variable, just changes it).  Maybe something could be hacked with
add-variable-watcher (not sure if it's a good idea though).