From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 14502@debbugs.gnu.org, rrt@sc3d.org
Subject: bug#14502: 24.3; dired-load-hook should not be customizable
Date: Wed, 22 Jan 2020 13:27:41 +0100 [thread overview]
Message-ID: <874kwnzneq.fsf@gnus.org> (raw)
In-Reply-To: <CABczVwdWtr2qvS+HXz4ENKPCkKsgZt9BNQ7P_7oEANpez3bULQ@mail.gmail.com> (Mauro Aranda's message of "Tue, 31 Dec 2019 10:41:11 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> I think this solution would be good. As for the controversial part, I
> think it would be possible to add some specific option that controls
> whether to overwrite or not a hook when using Customize. Also, a
> checkbox could toggle that option when customizing a hook interactively.
>
> But one problem is that using defcustom for the option would complicate
> things a little more than using plain defvar. For starters, every
> hook would have to have a :set-after property with that option.
Whatever solution we have should work generally and consistently. So
defcustoms of type `hook' should either overwrite (as they do currently)
or not (which would be more logical, perhaps).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-01-22 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 13:04 bug#14502: 24.3; dired-load-hook should not be customizable Reuben Thomas
2019-08-15 4:42 ` Lars Ingebrigtsen
[not found] ` <CAOnWdoh8TJRpPTiizOZf+RT=wKA45ztc+q_j+dq-9_190=gMWg@mail.gmail.com>
2019-08-16 1:29 ` Lars Ingebrigtsen
2019-08-16 8:13 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-08-16 20:50 ` Lars Ingebrigtsen
2020-10-28 8:53 ` Stefan Kangas
2019-12-31 13:41 ` Mauro Aranda
2020-01-22 12:27 ` Lars Ingebrigtsen [this message]
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=874kwnzneq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14502@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
--cc=rrt@sc3d.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.