all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 24023@debbugs.gnu.org
Subject: 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)	[thread overview]
Message-ID: <f8be0bca-adb4-461f-8e52-11a4add481db@default> (raw)
In-Reply-To: <<83bn1t1w7h.fsf@gnu.org>>

> 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').





       reply	other threads:[~2016-07-19 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<013bc8d5-e959-4814-9f31-bc9297499588@default>
     [not found] ` <<83bn1t1w7h.fsf@gnu.org>
2016-07-19 15:47   ` Drew Adams [this message]
2016-07-19  3:55 bug#24023: 24.5; Use `custom-file' (if defined), not init file, for `en/disable-command' Drew Adams
2016-07-19 15:30 ` Eli Zaretskii
2016-07-19 15:42   ` Glenn Morris
2016-07-19 15:48     ` Drew Adams

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

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

  git send-email \
    --in-reply-to=f8be0bca-adb4-461f-8e52-11a4add481db@default \
    --to=drew.adams@oracle.com \
    --cc=24023@debbugs.gnu.org \
    --cc=eliz@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.