unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: 8221@debbugs.gnu.org
Subject: bug#8221: 24.0.50; Allowed names for the init file. Windows/POSIX inconsistence.
Date: Thu, 10 Mar 2011 22:36:41 +0100	[thread overview]
Message-ID: <AANLkTikpJU24TQfF9CZpyNtnBj-03TQ3rZNsEyukHYxC@mail.gmail.com> (raw)

Severity: wishlist

Hello,

I've been reading the documented behavior of Emacs with respect to the
way it looks for the init file during startup.  This is explained in
the nodes "Init File" (for POSIX systems, I guess) and "Windows HOME" (for
MS Windows platforms).

According to the documentation (and the quick test I've done), we have this:
- On Windows systems, Emacs tries to find the init file by cheking (in
  several paths) for the existence of a file named `.emacs'.
- On POSIX systems, Emacs accepts the following alternatives as init
  file: `~/.emacs', `~/.emacs.el', or `~/.emacs.d/init.el'

So, the question is, why this inconsistence? i.e., why not accept on
Windows the same alternatives for the name of the init file as on
POSIX systems?

For example: Why not accept "<path>\.emacs.d\.init.el" as a valid init
file on Windows? (<path> being _any_ of the directories that Emacs
currently checks for the `.emacs' file)


-- 
Dani Moncayo





             reply	other threads:[~2011-03-10 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 21:36 Dani Moncayo [this message]
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
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=AANLkTikpJU24TQfF9CZpyNtnBj-03TQ3rZNsEyukHYxC@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=8221@debbugs.gnu.org \
    /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).