Issue783

classification
Title Bug reports should list non-default customizations.
Type feature Module core code 21.5
Severity some work obstructed Platform N/A
Keywords Nosy List stephen
explanation
process
These controls should only be changed by committers and tracker administrators.
Status new   Reason
Superseder  
Priority normal   Assigned To

Created on 2011-07-12.04:11:20 by stephen, last changed 2011-07-12.04:11:20 by stephen.

Messages
msg2334 [hidden] ([hidden]) Date: 2011-07-12.04:11:20
From a conversation with Tim Cross (for context, see the thread "Change
`customize-save-variable' to work under 'emacs -Q'?" on emacs-devel on
2011-07-12).

 > The core issue I see is that -Q is useful mainly because it
 > establishes a standard default environment.
[...]
 > Once we allow local customizations to be applied in this
 > environment, this standard base default environment no longer
 > exists. This may be fine, provided there is some mechanism that
 > makes what has been changed explicit and easy to reproduce.

I think that Customize already provides some function for listing
variables that are not at their default values, both Customized and
"rogue" values.  Its output could be added to the bug-reporter's buffer
(maybe it's already there in Emacs, but XEmacs doesn't do that yet). 
Perhaps it should be glossed with a comment that only defcustoms can be
listed this way.
History
Date User Action Args
2011-07-12 04:11:20stephencreate