unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
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 00:35:54 +0100	[thread overview]
Message-ID: <AANLkTikLM5+2J4J+D0ykL8KA4+eczx2nvX5a8MuhiaB5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin0b29-tM-+eg6SA6ZM_Rwd411tF+TvJA-j5wGq@mail.gmail.com>

On Thu, Mar 10, 2011 at 23:59, Jason Rumney <jasonr@gnu.org> wrote:
> Dani Moncayo <dmoncayo@gmail.com> writes:
>
>> 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?
>
> We do.
>

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.

On the other hand, and according to the same info node, C:\ is checked
as one possible "home" directory. 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.

-- 
Dani Moncayo





  reply	other threads:[~2011-03-10 23:35 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 [this message]
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=AANLkTikLM5+2J4J+D0ykL8KA4+eczx2nvX5a8MuhiaB5@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=8221@debbugs.gnu.org \
    --cc=jasonr@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).