From: Christopher Dimech <dimech@gmx.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ~/.emacs vs ~/.emacs.d/init.el.
Date: Sun, 13 Dec 2020 10:06:52 +0100 [thread overview]
Message-ID: <trinity-2b05786d-2446-426f-946e-2a96de1c8602-1607850412704@3c-app-mailcom-bs09> (raw)
In-Reply-To: <CAGP6PO+giFkvkTNn3KVFPL-MRxafqAdWSfUaQwmdah0XWC+A1g@mail.gmail.com>
You can have your own set of files for emacs customisation, then
use ~/.emacs or ~/.emacs.d/init.el to load them.
It would give you clear distinction between your customisation
and customizations that emacs itself can generate.
Using ~/.emacs is somewhat easier because it is also the location
of your ".bashrc".
C*
> Sent: Sunday, December 13, 2020 at 10:00 AM
> From: "Hongyi Zhao" <hongyi.zhao@gmail.com>
> To: help-gnu-emacs@gnu.org
> Subject: ~/.emacs vs ~/.emacs.d/init.el.
>
> Hi,
>
> As far as the initialization file is concerned, which is more
> preferable,~/.emacs or ~/.emacs.d/init.el?
>
> Regards
> --
> Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
> Theory and Simulation of Materials
> Hebei Polytechnic Vocational and Technical University
> NO. 552 North Gangtie Road, Xingtai, China
>
>
next prev parent reply other threads:[~2020-12-13 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 9:00 ~/.emacs vs ~/.emacs.d/init.el Hongyi Zhao
2020-12-13 9:06 ` Christopher Dimech [this message]
2020-12-13 10:09 ` Yuri Khan
2020-12-13 13:50 ` Hongyi Zhao
2020-12-13 13:56 ` Tim Visher
2020-12-13 13:58 ` 2QdxY4RzWzUUiLuE
2020-12-13 14:38 ` Hongyi Zhao
2020-12-13 14:44 ` Tim Visher
2020-12-13 14:52 ` 2QdxY4RzWzUUiLuE
2020-12-13 15:04 ` Tim Visher
2020-12-13 15:12 ` Hongyi Zhao
2020-12-13 18:58 ` 2QdxY4RzWzUUiLuE
2020-12-13 19:12 ` Eli Zaretskii
2020-12-13 14:06 ` Perry Smith
2020-12-13 14:31 ` Hongyi Zhao
2020-12-13 19:12 ` 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=trinity-2b05786d-2446-426f-946e-2a96de1c8602-1607850412704@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@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.
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).