unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, shanks.n@gmail.com
Subject: Re: C:\_emacs not being read
Date: Sun, 10 Jun 2007 23:46:15 +0100	[thread overview]
Message-ID: <466C7F37.7070505@gnu.org> (raw)
In-Reply-To: <ur6ojk5ng.fsf@gnu.org>

Eli Zaretskii wrote:
>> Date: Sun, 10 Jun 2007 09:25:33 +0100
>> From: Jason Rumney <jasonr@gnu.org>
>> Cc: shanks.n@gmail.com, bug-gnu-emacs@gnu.org
>>
>> I don't remember what the exact reason for not supporting it in this
>> particular place was.  I can't find the thread where we were discussing
>> it, only earlier threads from Nov 04 and May 05.
>>     
>
> I don't even remember this being discussed.
>   

Then perhaps it was an oversight. I thought I remembered some problem
being brought up in checking for both names in c:\.

> What about startup.el?  If HOME _is_ set, we still try to load _emacs
> if there's no .emacs there.
>   

The intention was definitely never to drop support for _emacs
completely, but I thought I remembered a discussion about problems with
checking in multiple locations, which was resolved by deprecating the
non-standard _emacs version.

> If you mean remove this from the manual only as a deprecation measure,
> then we probably should introduce it into w32.c where we check for
> C:/.emacs.

If 22.2 is to be released soon, then it is worth adding a check if we
are sure it is an omission.

  reply	other threads:[~2007-06-10 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-09 15:52 C:\_emacs not being read Shanks N
2007-06-09 21:16 ` Jason Rumney
2007-06-10  3:07   ` Eli Zaretskii
2007-06-10  5:08     ` Drew Adams
2007-06-10  8:25     ` Jason Rumney
2007-06-10 18:48       ` Eli Zaretskii
2007-06-10 22:46         ` Jason Rumney [this message]
2007-06-10 13:18     ` Richard Stallman
2007-06-10 18:57       ` Eli Zaretskii
2007-06-10 22:37       ` Jason Rumney

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=466C7F37.7070505@gnu.org \
    --to=jasonr@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@gnu.org \
    --cc=shanks.n@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).