From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 13780@debbugs.gnu.org, monnier@iro.umontreal.ca, rrt@sc3d.org
Subject: bug#13780: 24.2; Making find-file-hook customizable seems to cause troublle
Date: Wed, 25 Nov 2020 17:19:43 +0200 [thread overview]
Message-ID: <83sg8xsbu8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnav+rwJxNTW-ibC1q5zbghZyOFscNzE1irERoiS4h8Mg@mail.gmail.com> (message from Stefan Kangas on Tue, 24 Nov 2020 18:18:58 -0800)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 24 Nov 2020 18:18:58 -0800
> Cc: 13780@debbugs.gnu.org, monnier@iro.umontreal.ca, rrt@sc3d.org
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> >>> So until Custom is fixed to actually properly handle customisation of
> >>> hooks (e.g. by storing "add functions foo, bar, and baz" rather than
> >>> "ignore current value and just set it to (foo bar baz)").
> >> This sentence seems to be missing its main clause…
> >
> > That's not just an appearance. Its main clause is:
> >
> > So until Custom ...blabla... I think it's better to use defcustom for
> > hooks very sparingly, i.e. only for those hook we can reasonably
> > expect will only be modified by the user's customization.
IMO, this rationale is good for future additions, not for
already-existing user options. We cannot un-defcustom a user option
just because someone became confused by some subtle use case. This is
the price we pay for the flexibility and power we have in Emacs.
next prev parent reply other threads:[~2020-11-25 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 0:33 bug#13780: 24.2; Making find-file-hook customizable seems to cause troublle Reuben Thomas
2013-02-22 2:14 ` Stefan Monnier
2013-02-22 11:43 ` Reuben Thomas
2013-02-22 14:22 ` Stefan Monnier
2013-02-22 19:38 ` Reuben Thomas
2013-02-22 20:58 ` Stefan Monnier
2020-10-28 8:52 ` Stefan Kangas
2020-10-28 15:15 ` Eli Zaretskii
2020-11-25 2:18 ` Stefan Kangas
2020-11-25 15:19 ` Eli Zaretskii [this message]
2020-11-25 21:07 ` Stefan Kangas
2020-12-04 11:05 ` Stefan Kangas
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=83sg8xsbu8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13780@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rrt@sc3d.org \
--cc=stefan@marxist.se \
/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).