From: Robert Pluim <rpluim@gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: 54381@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#54381: 29.0.50; Automatically load custom-file
Date: Mon, 14 Mar 2022 18:53:46 +0100 [thread overview]
Message-ID: <87pmmocted.fsf@gmail.com> (raw)
In-Reply-To: <CAO48Bk989kuXyW2+mgA34WAVdwd2jsf=YkvfySPqYJpNM-=E=g@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Mon, 14 Mar 2022 17:47:49 +0100")
>>>>> On Mon, 14 Mar 2022 17:47:49 +0100, Pedro Andres Aranda Gutierrez <paaguti@gmail.com> said:
Pedro> Robert > No, I donʼt think that would be a good idea: thereʼs a "custom.el"
Pedro> in
Robert> the emacs sources already, and we should indicate somehow that this
Pedro> is
Robert> *data*, not code.
Pedro> Don't follow you here. My customization file '~/.emacs.d/custom.el' is
Pedro> code, isn't it?
Yes, thereʼs no distinction between code and data in lisp. But your
custom file should only contain `custom-set-variables' and
`custom-set-faces', not any old lisp forms.
Robert
--
next prev parent reply other threads:[~2022-03-14 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 8:21 bug#54381: 29.0.50; Automatically load custom-file Pedro Andres Aranda Gutierrez
2022-03-14 9:47 ` Lars Ingebrigtsen
2022-03-14 9:48 ` Lars Ingebrigtsen
2022-03-14 15:14 ` bug#54381: [External] : " Drew Adams
2022-03-14 13:15 ` Eli Zaretskii
2022-03-14 15:26 ` Robert Pluim
2022-03-14 16:19 ` Pedro Andres Aranda Gutierrez
2022-03-14 16:36 ` Robert Pluim
2022-03-14 16:47 ` Pedro Andres Aranda Gutierrez
2022-03-14 17:53 ` Robert Pluim [this message]
2022-03-15 7:51 ` Pedro Andres Aranda Gutierrez
2022-03-14 13:58 ` Robert Pluim
2022-04-14 14:05 ` Lars Ingebrigtsen
2022-03-17 6:38 ` bug#54381: Handling a corner case Pedro Andres Aranda Gutierrez
2022-03-17 7:09 ` Pedro Andres Aranda Gutierrez
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=87pmmocted.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=54381@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=paaguti@gmail.com \
/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.