From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: User setup for emacs
Date: Sun, 10 Oct 2021 18:45:03 +0200 [thread overview]
Message-ID: <875yu44ynk.fsf@zoho.eu> (raw)
In-Reply-To: hqEIaNpAK7bMRUuQbFeOtF2mDsO4ad8Yj4kMRrb48DT5CNkzPNJtCyzzUHLW0_9qDLI6Pk0_2wPZQZ37FNdhzTrdDhpjuem9Zu44RE-fRIc=@protonmail.com
tolugboji wrote:
>> Your posts don't look good BTW ...
>
> I work to improve them and for others to find useful
> information. I do not see that emacs provides a .emacs
> dering installation.
It doesn't if you by installation mean the placing of binaries
etc in $PATH directories and such stuff ...
But I like it that way, I don't like when Emacs adds stuff to
my init files and I see no advantage of that, on the contrary
I'd keep that human/computer separation clean.
Also I have no idea why this "has to" be the way it is but
with this at least I don't have to see it
(setq custom-file "~/ooa/dork.elc")
I don't even use custom so why can't that be opted out
completely? Or can it? Apologies if so ...
> The article claims that the latest way to include
> customisations is via ~/.emacs.d/init.el rather than using
> ~/.emacs. Is this claim correct?
Well, to me the init files were just files, the only thing
setting .emacs apart is that Emacs by default looks for it,
i.e., looks for a file located in $HOME with that name.
But I don't know, maybe there is indeed a policy which is
wholly or in part enforced somehow with respect to specific
files ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-10-10 16:45 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 [this message]
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
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=875yu44ynk.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).