unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	Peter Oliver <p.d.oliver@mavit.org.uk>,
	49424@debbugs.gnu.org
Subject: bug#49424: 27.2; Misdocumented default initialisation file
Date: Wed, 07 Jul 2021 16:11:32 +0200	[thread overview]
Message-ID: <871r8a43jf.fsf@gmx.net> (raw)
In-Reply-To: <87sg0qb7ay.fsf@gmail.com> (Robert Pluim's message of "Wed, 07 Jul 2021 15:08:21 +0200")

On Wed, 07 Jul 2021 15:08:21 +0200 Robert Pluim <rpluim@gmail.com> wrote:

>>>>>> On Thu, 08 Jul 2021 00:24:22 +1200, Phil Sainty <psainty@orcon.net.nz> said:
>
>     Phil> On 2021-07-07 21:17, Robert Pluim wrote:
>     >> If nothing exists, Emacs will create ~/.emacs.d, and use ~/.emacs as
>     >> as the init file. We can change that to use ~/.emacs.d/init.el if we
>     >> want, people who already have init files will not be affected.
>     >> </bold prediction of there being no consequences>
>
>     Phil> I know of people who have ~/.emacs.d under version control (used on
>     Phil> multiple machines), and on some machines additionally have a ~/.emacs
>     Phil> file for config which is local to that particular machine.  The .emacs
>     Phil> file simply loads the init.el file.
>
> Thatʼs a different branch of the startup logic :-)
>
> If we change things so that ~/.emacs.d/init.el is used only if there
> is no .emacs, they would not be affected. I think this is already
> the case, but I may be misremembering
>
>     Phil> There are other ways of achieving the same thing; but I thought this
>     Phil> one was quite a neat approach when I heard it.
>
>     Phil> In other words, FYI some people's configs are definitely reliant on
>     Phil> the current precedence order.
>
>     Phil> In any case, while the sequence *could* be changed for those two
>     Phil> files, I don't think there's any notable benefit to doing so?  Even
>     Phil> ignoring cases like the one above, that change would undoubtedly
>     Phil> cause some confusion for no good reason.
>
> Iʼm not proposing changing the sequence, only what happens in the case
> where there are no init files at all. It would eliminate the 'why is
> emacs creating .emacs.d but then not using it' confusion.

One thing I find useful about the current way is that I can use ~/.emacs
to carry out tests requiring (or facilitated by having) an init file,
without having to move or otherwise disable my actual init file
~/.emacs.d/init.el.  That benefit would be lost if the priority was
changed (or it would require making ~/.emacs the real init file and
using ~/.emacs.d/init.el for testing, which seems less appealing).

Steve Berman





  reply	other threads:[~2021-07-07 14:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 22:56 bug#49424: 27.2; Misdocumented default initialisation file Peter Oliver
2021-07-06 15:11 ` Lars Ingebrigtsen
2021-07-07  9:17   ` Robert Pluim
2021-07-07 11:28     ` Rudolf Schlatte
2021-07-07 13:10       ` Robert Pluim
2021-07-07 16:33         ` Rudolf Schlatte
2021-07-07 12:24     ` Phil Sainty
2021-07-07 13:08       ` Robert Pluim
2021-07-07 14:11         ` Stephen Berman [this message]
2021-07-07 14:40           ` Robert Pluim
2021-07-07 16:21             ` Stephen Berman
2021-07-08  1:06         ` Phil Sainty
2021-07-07 17:58     ` Peter Oliver
2021-07-08  1:17       ` Phil Sainty
2021-07-08  7:23         ` Eli Zaretskii
2021-07-08  8:30           ` Robert Pluim
2021-07-08  9:21             ` Eli Zaretskii
2021-07-07 18:12     ` Peter Oliver
2021-07-07 18:36       ` Eli Zaretskii
2021-07-07 19:08         ` Peter Oliver
2021-07-07 19:27           ` Eli Zaretskii
2021-07-07 21:51             ` Peter Oliver
2021-07-08  6:23               ` Eli Zaretskii
2021-07-08  8:40                 ` Robert Pluim
2021-07-08  9:22                   ` Eli Zaretskii
2021-07-08 18:22                     ` Peter Oliver
2021-07-08 19:10                       ` Eli Zaretskii
2021-10-24  8:12                 ` Stefan Kangas
2021-10-24 13:27                   ` Lars Ingebrigtsen
2021-10-24 14:10                     ` Stefan Kangas
2021-10-24 14:17                       ` Lars Ingebrigtsen
2021-10-24 14:47                         ` Stefan Kangas
2021-10-24 14:56                         ` Stefan Kangas
2021-10-24 15:20                           ` Eli Zaretskii
2021-10-24 21:52                             ` Stefan Kangas
2021-10-24 14:25                   ` Robert Pluim

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=871r8a43jf.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=49424@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=p.d.oliver@mavit.org.uk \
    --cc=psainty@orcon.net.nz \
    --cc=rpluim@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 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).