GNU bug report logs - #24023
24.5; Use `custom-file' (if defined), not init file, for `en/disable-command'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Tue, 19 Jul 2016 03:56:02 UTC

Severity: wishlist

Merged with 5974

Found in version 24.5

Full log


Message #16 received at 24023 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Drew Adams <drew.adams <at> oracle.com>
Cc: 24023 <at> debbugs.gnu.org
Subject: RE: bug#24023: 24.5; Use `custom-file' (if defined), not init file,
 for	`en/disable-command'
Date: Tue, 19 Jul 2016 08:47:40 -0700 (PDT)
> This feature is not a defcustom, so it doesn't work like one.  Perhaps
> the easiest way forward would be to make it a defcustom, or something
> like one.

I see now that this was all discussed in the bug that this one was merged with. I'd forgotten about that bug.

Yes, something should be done, to bring this feature up to the level of current Emacs.  A priori, I don't really care what is done or how.  IOW, I trust your judgment on this.

The point is that Emacs should not still be writing to a users init file.  As mentioned in that other bug thread, two alternative suggestions were:

* Replace this way of enabling/disabling with a way that uses defcustom.  (It could involve a wrapper around the `put' thingy or something else.)

* Keep the current mechanism, but write to a different file from the init file (and different from `custom-file').




This bug report was last modified 8 years and 330 days ago.

Previous Next


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