From: Eli Zaretskii <eliz@gnu.org>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: larsi@gnus.org, 49424@debbugs.gnu.org, rpluim@gmail.com
Subject: bug#49424: 27.2; Misdocumented default initialisation file
Date: Wed, 07 Jul 2021 21:36:01 +0300 [thread overview]
Message-ID: <831r8aezu6.fsf@gnu.org> (raw)
In-Reply-To: <995892f5-e466-ada6-a64a-e1199d4e33a6@froglet.home.mavit.org.uk> (message from Peter Oliver on Wed, 7 Jul 2021 19:12:03 +0100 (BST))
> Date: Wed, 7 Jul 2021 19:12:03 +0100 (BST)
> From: Peter Oliver <p.d.oliver@mavit.org.uk>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 49424@debbugs.gnu.org
>
> > Yes, we should change that to say '~/.emacs'
>
> Here’s a patch to do that.
>
> --
> Peter Oliver
>
> From e0a95ea7a048c505820829d8e10f0addf2cc6c4a Mon Sep 17 00:00:00 2001
> From: Peter Oliver <git@mavit.org.uk>
> Date: Wed, 7 Jul 2021 19:09:58 +0100
> Subject: [PATCH] Document init file with the highest precedence as ~/.emacs
>
> * doc/emacs/custom.texi: Default location of init file is ~/.emacs
> (bug#49424).
> ---
> doc/emacs/custom.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
> index de5d825248..708349e833 100644
> --- a/doc/emacs/custom.texi
> +++ b/doc/emacs/custom.texi
> @@ -2713,7 +2713,7 @@ Find Init
> name in the system's data base of users.
>
> For brevity the rest of the Emacs documentation generally uses just
> -the current default location @file{~/.emacs.d/init.el} for the
> +the current default location @file{~/.emacs} for the
> init file.
Thanks, but this is still inaccurate. Can we please change the
documentation so that it tells the whole story?
next prev parent reply other threads:[~2021-07-07 18:36 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
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 [this message]
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=831r8aezu6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49424@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=p.d.oliver@mavit.org.uk \
--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).