From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: why do some programming modes have customize hooks and others do not?
Date: Mon, 20 Oct 2014 11:38:33 +0100 [thread overview]
Message-ID: <CAAdUY-L8MMmVakXxhUhpZEMQx_vA1Z4kw-+Q4bJnJ4qYfrVn-g@mail.gmail.com> (raw)
In-Reply-To: <871tq36tpl.fsf@ferrier.me.uk>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
> If I sent patches (once we're on git, how goes that?) for customize any
> hooks that aren't already customizable, they would get accepted?
I'd like to point out that saving a hook with the customize interface is
kind of asking for trouble.
Hooks are routinely added by arbitrary packages. If an unsuspecting user
customizes and saves a hook through the customize interface, any functions
that other packages have added to it will be saved as well.
If the user later removes one of these packages, he'll be confronted with
"undefined function" errors which no amount of restarting will solve.
The safe (and annoying) way to do this would be to define a second hook for
the user, and make that a defcustom.
Malabarba
[-- Attachment #2: Type: text/html, Size: 852 bytes --]
next prev parent reply other threads:[~2014-10-20 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 11:10 why do some programming modes have customize hooks and others do not? Nic Ferrier
2014-10-18 11:37 ` Bastien
2014-10-18 21:46 ` Stefan Monnier
2014-10-18 22:24 ` Nic Ferrier
2014-10-19 22:44 ` Rüdiger Sonderfeld
2014-10-20 2:15 ` Stefan Monnier
2014-10-20 8:17 ` Nic Ferrier
2014-10-20 10:38 ` Artur Malabarba [this message]
2014-10-20 10:54 ` Nic Ferrier
2014-10-20 12:07 ` Artur Malabarba
2014-10-20 16:47 ` Stefan Monnier
2014-10-20 18:29 ` Nic Ferrier
2014-10-20 16:02 ` Stefan Monnier
2014-10-20 19:11 ` Nic Ferrier
2014-10-20 20:39 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAdUY-L8MMmVakXxhUhpZEMQx_vA1Z4kw-+Q4bJnJ4qYfrVn-g@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nferrier@ferrier.me.uk \
--cc=ruediger@c-plusplus.de \
/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.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).