From: tolugboji <tolugboji@protonmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eduardo Ochs <eduardoochs@gmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: User setup for emacs
Date: Sun, 10 Oct 2021 18:35:51 +0000 [thread overview]
Message-ID: <e4wbnCC8SX20OCeZmuS8KOwjT1XbIDo9ggg1_2Llax3orkVQWFmS1OAP9J5dZ_-NljxZ4_8ObX1xzgVzJFbVknsbzL3uTbPCxZbnahVMIw0=@protonmail.com> (raw)
In-Reply-To: <SJ0PR10MB54887F0C915AD8F17D3E72D4F3B49@SJ0PR10MB5488.namprd10.prod.outlook.com>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, October 10th, 2021 at 6:31 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > I set custom-file to another file - ~/.emacs.custom - because I don't
> >
> > understand customize well and I used to feel very scared everytime
> >
> > that customize changed something in my ~/.emacs without showing me
> >
> > what it was doing. The part of my ~/.emacs that sets this is:
> >
> > (setq custom-file "~/.emacs.custom")
> >
> > (load custom-file)
>
> IMHO, everyone should define `custom-file', and thus keep Customize's maintenance of the code it generates away from the code you write in your init file. To me, this is common sense. But I was unable to get Emacs to even recommend using` custom-file', let alone programmatically
>
> encourage (not quite enforce) its use.
Quite unfortunate. It takes a lot of convincing and changes very slow.
I would like to ask if the link to the user-customisation files should
be done from ~/.emacs.d/init.el.
Is the latest way to do so in ~/.emacs.d/init.el rather than from ~/.emacs?
next prev parent reply other threads:[~2021-10-10 18:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 15:30 User setup for emacs tolugboji via Users list for the GNU Emacs text editor
2021-10-08 16:16 ` tolugboji
2021-10-09 10:03 ` tolugboji
2021-10-10 14:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 14:33 ` tolugboji
2021-10-10 15:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 15:47 ` tolugboji
2021-10-10 16:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 17:11 ` tolugboji
2021-10-11 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 1:23 ` tolugboji
2021-10-11 3:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 18:00 ` Eduardo Ochs
2021-10-10 18:14 ` tolugboji
2021-10-10 18:31 ` [External] : " Drew Adams
2021-10-10 18:35 ` tolugboji [this message]
2021-10-10 19:02 ` [External] : " Drew Adams
2021-10-10 19:11 ` tolugboji
2021-10-11 0:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-10 23:59 ` [External] : " Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 0:34 ` Drew Adams
2021-10-11 3:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
[not found] ` <SJ0PR10MB5488088380C0302344DA8E15F3B59@SJ0PR10MB5488.namprd10.prod.outlook.com>
[not found] ` <87r1cr1ql2.fsf@zoho.eu>
2021-10-11 16:30 ` Drew Adams
2021-10-11 16:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 16:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-11 16:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
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='e4wbnCC8SX20OCeZmuS8KOwjT1XbIDo9ggg1_2Llax3orkVQWFmS1OAP9J5dZ_-NljxZ4_8ObX1xzgVzJFbVknsbzL3uTbPCxZbnahVMIw0=@protonmail.com' \
--to=tolugboji@protonmail.com \
--cc=drew.adams@oracle.com \
--cc=eduardoochs@gmail.com \
--cc=help-gnu-emacs@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.
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).