From: Dani Moncayo <dmoncayo@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 8221@debbugs.gnu.org
Subject: bug#8221: 24.0.50; Allowed names for the init file. Windows/POSIX inconsistency
Date: Fri, 11 Mar 2011 09:26:20 +0100 [thread overview]
Message-ID: <AANLkTi=3TQ0sUyzWHhEJQ3p4PNWvowi3bsoK86Wvx+ek@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimAVWPJ74sgGUpV9n4oEF=bqr9mqkPs3fY01Pu+@mail.gmail.com>
Hi Juanma,
On Fri, Mar 11, 2011 at 03:49, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Fri, Mar 11, 2011 at 00:35, Dani Moncayo <dmoncayo@gmail.com> wrote:
>
>> On one hand, it doesn't seem to be the documented behavior in the node
>> "Windows HOME" of the manual. It refers to the init file as `.emacs',
>> and says nothing about possible alternatives.
>
> The alternatives are documented on "53.6 The Init File, `~/.emacs'";
> there's no need to duplicate it on "G.5 HOME and Startup Directories
> on MS-Windows".
>
Indeed, that is the node which explains the alternatives, and of
course I agree that such info shouldn't be duplicated in any other
node of the Manual. Instead of duplicating, the others nodes (IMO)
should refer to the init file as `init file' (maybe giving a link to
the suitable node), but not as `.emacs', as we currently have in node
"Windows HOME".
>> On the other hand, and according to the same info node, C:\ is checked
>> as one possible "home" directory.
>
> I think you're reading more that the info node says. What it says is
> that Emacs is looking for HOME (the environment variable) and if it
> finds it, it looks there for the "init file". If that fails, it looks
> for ".emacs" in C:\; and if that fails, it looks for the AppData dir
> (which is an alternative to HOME, not to C:\). So it is clear (if a
> bit inconsistent) that looking for .emacs (specifically) on C:\
> (specifically) is something done just because of back compatibility.
>
Yes, I got a bit confused about the exact procedure. Maybe I was
somewhat biased, but IMO the current wording is a bit confusing:
> The home directory is where your init file `.emacs' is stored. When
> Emacs starts, it first checks whether the environment variable `HOME'
> is set. If it is, it looks for the init file in the directory pointed
> by `HOME'. If `HOME' is not defined, Emacs checks for an existing
> `.emacs' file in `C:\', the root directory of drive `C:'(1). If
> there's no such file in `C:\', Emacs next uses the Windows system calls
> to find out the exact location of your application data directory. If
> that system call fails, Emacs falls back to `C:\'.
That made me think that the principle was (a) Try to find a suitable
init file in several directories, and (b) Once an init file is found,
the "home" directory is thereafter established accordingly.
Thus, I suggest to revise the wording in that node, to avoid this confusion.
>> Thus, init files such as
>> "C:\.emacs.el" or "C:\.emacs.d\init.el" should be valid ones. But I've
>> just tested those two and Emacs don't find them.
>
> If you ask me, not even C:\.emacs should be valid; "set HOME=C:\"
> should be required for that.
>
I agree, because IMO the init file should always be user-specific, and
C:\ isn't a user-specific directory.
--
Dani Moncayo
next prev parent reply other threads:[~2011-03-11 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 21:36 bug#8221: 24.0.50; Allowed names for the init file. Windows/POSIX inconsistence Dani Moncayo
2011-03-10 22:17 ` bug#8221: 24.0.50; Allowed names for the init file. Windows/POSIX inconsistency Dani Moncayo
2011-03-10 23:35 ` Dani Moncayo
2011-03-11 2:49 ` Juanma Barranquero
2011-03-11 8:26 ` Dani Moncayo [this message]
2011-03-11 11:22 ` Eli Zaretskii
2011-03-11 11:26 ` Eli Zaretskii
2011-03-10 22:59 ` bug#8221: 24.0.50; Allowed names for the init file. Windows/POSIX inconsistence Jason Rumney
2011-03-11 2:40 ` Juanma Barranquero
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='AANLkTi=3TQ0sUyzWHhEJQ3p4PNWvowi3bsoK86Wvx+ek@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=8221@debbugs.gnu.org \
--cc=lekktu@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).