emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: strange behaviour when customising org-agenda-custom-commands
Date: Sun, 30 Dec 2007 19:47:07 +0000	[thread overview]
Message-ID: <20071230194707.GG20947@atlantic.linksys.moosehall> (raw)
In-Reply-To: <20071217140115.GF13112@atlantic.linksys.moosehall> <20071210112539.GH15129@atlantic.linksys.moosehall>

[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?

  parent reply	other threads:[~2007-12-30 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  0:55 strange behaviour when customising org-agenda-custom-commands Adam Spiers
     [not found] ` <C4B91C21-205E-48BC-9939-E58D6A80AA6C@science.uva.nl>
     [not found]   ` <20071208183046.GC15129@atlantic.linksys.moosehall>
     [not found]     ` <20071210112539.GH15129@atlantic.linksys.moosehall>
     [not found]       ` <acf852aa0712170449r3168ab73p1e348bb687773e96@mail.gmail.com>
     [not found]         ` <20071217140115.GF13112@atlantic.linksys.moosehall>
2007-12-30 19:47           ` Adam Spiers [this message]
2007-12-30 21:32             ` Adam Spiers
2008-01-04 22:13               ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071230194707.GG20947@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).