From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Settings
Date: Fri, 30 Aug 2019 11:50:51 +0200 [thread overview]
Message-ID: <87ftljhthg.fsf@gnus.org> (raw)
In-Reply-To: <E1i2knY-0008T0-Ub@fencepost.gnu.org> (Richard Stallman's message of "Tue, 27 Aug 2019 19:22:48 -0400")
Richard Stallman <rms@gnu.org> writes:
> My point is that maybe we don't want to process all custom
> definitions in one single batch. If we can identify specific
> needs with regard to particular custom variables, we could
> do something more sophisticated, and MAYBE we could make that
> work right for every user without requiring that the user
> figure out a solution that works right for all of them.
It's possible, but I think that sounds... very ambitious. But I could
see the case for saying something general like "customising hook
variables should happen before loading .emacs, because that will make
add-hook work", but even that would be controversial. (Customising a
hook sets the variable to a specific value; it doesn't add functions.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-30 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 21:52 Settings Lars Ingebrigtsen
2019-08-15 23:11 ` Settings Drew Adams
2019-08-25 15:45 ` Settings Stefan Monnier
2019-08-25 16:30 ` Settings Drew Adams
2019-08-25 18:21 ` Settings Stefan Monnier
2019-08-26 4:18 ` Settings Lars Ingebrigtsen
2019-08-26 23:13 ` Settings Richard Stallman
2019-08-26 23:20 ` Settings Drew Adams
2019-08-27 23:22 ` Settings Richard Stallman
2019-08-30 9:50 ` Lars Ingebrigtsen [this message]
2019-08-31 2:54 ` Settings Richard Stallman
2019-08-27 6:20 ` Settings Eli Zaretskii
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=87ftljhthg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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 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).