From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Nicolas Richard <nrichard@ulb.ac.be>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 5974@debbugs.gnu.org
Subject: bug#5974: 23.1.95; enabling disabled cmd & saving doesn't respect `custom-file'
Date: Fri, 29 Apr 2016 09:31:39 -0700 (PDT) [thread overview]
Message-ID: <dc9618d1-e1fd-4feb-8545-101a0a5c2de1@default> (raw)
In-Reply-To: <87twik5vyq.fsf@gnus.org>
Please. You guys have hijacked this bug report to speculate
about using Customize to handle enabling/disabling commands
Please start a new bug thread - or better yet an emacs-devel
thread - for that.
THIS bug report is about the fact that if a user has a
`custom-file' the enabling gets recorded to ~/.emacs instead.
That's just plain wrong.
Surely this bug can be fixed independently of your thoughts
about a new design/feature for letting Customize handle
enabling more generally. You can always revisit this case
after you've implemented whatever you dream up for that,
but this bug is not that enhancement.
next prev parent reply other threads:[~2016-04-29 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 16:22 bug#5974: 23.1.95; enabling disabled cmd & saving doesn't respect `custom-file' Drew Adams
2010-04-19 17:06 ` Drew Adams
2010-04-19 17:22 ` Stefan Monnier
2016-04-27 21:53 ` Lars Ingebrigtsen
2016-04-28 10:41 ` Nicolas Richard
2016-04-28 22:57 ` Lars Ingebrigtsen
2016-04-28 23:08 ` Lars Ingebrigtsen
2016-04-29 14:21 ` Nicolas Richard
2016-04-29 14:30 ` Lars Ingebrigtsen
2016-04-29 16:31 ` Drew Adams [this message]
2016-04-29 20:20 ` Nicolas Richard
2016-04-29 22:32 ` Drew Adams
2016-04-29 22:39 ` Lars Ingebrigtsen
2016-04-29 23:11 ` 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=dc9618d1-e1fd-4feb-8545-101a0a5c2de1@default \
--to=drew.adams@oracle.com \
--cc=5974@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=nrichard@ulb.ac.be \
/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.