Re: [Orgmode] strange behaviour when customising org-agenda-custom-commands

[Adam Spiers]

[moving thread to the list in case anyone else can shed light]

Adam Spiers wrote:
> On Mon, Dec 17, 2007 at 01:49:49PM +0100, Carsten Dominik wrote:
> > On Dec 10, 2007 12:25 PM, Adam Spiers wrote:
> > > On Sat, Dec 08, 2007 at 06:30:46PM +0000, Adam Spiers wrote:
> > > > On Tue, Nov 13, 2007 at 12:38:06PM +0100, Carsten Dominik wrote:
> > > > > On  8Nov2007, at 1:55 AM, Adam Spiers wrote:
> > > > > > I haven't figured out how to reproduce this reliably yet, but there
> > > > > > seems to be a bug in 5.13h where when customizing
> > > > > > org-agenda-custom-commands, sometimes during a Set or Save (not sure
> > > > > > which) all the prefix key documentation entries vanish.  Any ideas 
> > > > > > why
> > > > > > this would happen?
> > > > >
> > > > > any more constraints on this?
> > > >
> > > > Not yet sorry - when I find time to finishing customization of
> > > > org-agenda-custom-commands off, I'll try to debug it more fully and
> > > > let you know.
> > > 
> > > I think I may have figured it out as being a general issue with emacs
> > > custom mode.  If you edit a custom variable as a lisp expression, then
> > > change back to normal view without doing "Set for Current Session"
> > > then it loses all the changes you made to the elisp sexp.  Can you
> > > reproduce that?
> > 
> > I don't even need to check, this is how customize is supposed to work.
> > Before using set for current session, nothing changes internally, and
> > when you switch to a different view, th current internal value is used
> > to produce the view.
> 
> Yep, I should have guessed from the wording "Show Saved Lisp
> Expression".  I'm pretty sure this is what caused the loss of config,
> but if I see it still happening I'll let you know.  Thanks.

Argh, it just happened again with 5.17a!  And it was definitely only
(and all) the prefix key documentation entries which vanished, such as

   ("#" . "TODOs by priority")

Additionally I have been most careful to regularly save customizations
since the discussion above, so I'm now sure that there is a bug
somewhere after all; I just don't know how to trigger it.  Is the
defcustom definition for prefix key documentation definitely correct?