From: Eli Zaretskii <eliz@fencepost.gnu.org>
Cc: eggert@twinsun.com, emacs-devel@gnu.org, knagano@sodan.org
Subject: Re: init_buffer PWD fix
Date: Wed, 24 Apr 2002 14:10:36 -0400 [thread overview]
Message-ID: <E170RDw-0007HY-00@fencepost.gnu.org> (raw)
In-Reply-To: <uhem1t3yd.fsf@MILCH.meadowy.org> (himi@meadowy.org)
> From: MIYASHITA
> Hisashi(=?ISO-2022-JP?B?GyRCNVwyPBsoQiAbJEI+MBsoQjpISU1J?=)
> <himi@meadowy.org>
> Date: Thu, 25 Apr 2002 02:13:30 +0900
>
> I can imagin many bad situations. Suppose the following
> situation as an example.
>
> (1) sh or tcsh set "PWD" and the current directory to "c:/PROGRA~1"
> (1) (this name is
> the short name of "c:/Program Files"), and then invokes a
> (1) program.
>
> (2) the invoked program set the current directory to "c:/Program
> (2) Files"
> by SetCurrentDirectory().
>
> (3) then it invokes Emacs.
>
> I confirmed that by invoking tcsh.exe -> cmd.exe -> emacs.exe.
>
> In this case, Emacs set the default directory to "c:/PROGRA~1",
> which is clearly
> different from the expected value.
I can throw together an example where the opposite is true: the value
of PWD is better than what GetCurrentDirectory returns.
In any case, both c:/PROGRA~1 and c:/Program Files point to the same
directory, so this is at best an aesthetic annoyance.
> I can agree on the current code on many
> UNIX systems. And surely it's convenient.
>
> On Windows, however, it's not only useless but also harmful, I
> think.
OTOH, differences in behavior on different platforms are not a good
idea, either. It makes the documentation either confusing or
incorrect, and it confuses people who need to work on several
different platforms.
next prev parent reply other threads:[~2002-04-24 18:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 20:15 init_buffer PWD fix Keiichiro Nagano
2002-04-21 23:00 ` Keiichiro Nagano
2002-04-22 6:18 ` Paul Eggert
2002-04-22 7:20 ` Keiichiro Nagano
2002-04-22 11:15 ` Eli Zaretskii
2002-04-22 21:16 ` Jason Rumney
2002-04-22 7:53 ` Eli Zaretskii
2002-04-22 7:01 ` Paul Eggert
2002-04-22 8:10 ` Eli Zaretskii
2002-04-22 7:22 ` Paul Eggert
2002-04-22 11:14 ` Eli Zaretskii
2002-04-22 23:21 ` Paul Eggert
2002-04-23 6:05 ` Eli Zaretskii
2002-04-22 21:21 ` Jason Rumney
2002-04-23 5:56 ` Eli Zaretskii
2002-04-23 6:14 ` MIYASHITA Hisashi
2002-04-23 11:00 ` Eli Zaretskii
2002-04-24 17:55 ` Richard Stallman
2002-04-24 18:14 ` MIYASHITA Hisashi
2002-04-23 17:45 ` Paul Eggert
2002-04-24 6:52 ` MIYASHITA Hisashi
2002-04-24 7:13 ` Paul Eggert
2002-04-24 7:45 ` MIYASHITA Hisashi
2002-04-24 11:12 ` Eli Zaretskii
2002-04-24 10:30 ` MIYASHITA Hisashi
2002-04-24 16:03 ` Eli Zaretskii
2002-04-24 17:13 ` MIYASHITA Hisashi
2002-04-24 18:10 ` Eli Zaretskii [this message]
2002-04-24 18:25 ` MIYASHITA Hisashi
2002-04-24 19:19 ` Paul Eggert
2002-04-24 19:41 ` MIYASHITA Hisashi
2002-04-24 19:59 ` MIYASHITA Hisashi
2002-04-24 20:21 ` Paul Eggert
2002-04-24 20:41 ` MIYASHITA Hisashi
2002-04-24 21:01 ` Paul Eggert
2002-04-24 21:23 ` MIYASHITA Hisashi
2002-04-24 21:35 ` MIYASHITA Hisashi
2002-04-25 22:52 ` Stefan Monnier
2002-04-25 3:42 ` Eli Zaretskii
2002-04-24 16:47 ` Paul Eggert
2002-04-24 17:55 ` MIYASHITA Hisashi
2002-04-24 10:38 ` MIYASHITA Hisashi
2002-04-24 16:08 ` Eli Zaretskii
2002-04-24 16:10 ` Eli Zaretskii
2002-04-24 7:55 ` MIYASHITA Hisashi
2002-04-24 11:07 ` Eli Zaretskii
2002-04-24 11:05 ` Eli Zaretskii
2002-04-24 10:31 ` MIYASHITA Hisashi
2002-04-24 16:05 ` Eli Zaretskii
2002-04-22 7:03 ` Eli Zaretskii
2002-04-22 6:49 ` Keiichiro Nagano
2002-04-22 8:01 ` Eli Zaretskii
2002-04-22 8:26 ` Keiichiro Nagano
2002-04-22 11:19 ` Eli Zaretskii
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=E170RDw-0007HY-00@fencepost.gnu.org \
--to=eliz@fencepost.gnu.org \
--cc=eggert@twinsun.com \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=knagano@sodan.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).