From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: MIYASHITA Hisashi(=?ISO-2022-JP?B?GyRCNVwyPBsoQiAbJEI+MBsoQjpISU1J?=) Newsgroups: gmane.emacs.devel Subject: Re: init_buffer PWD fix Date: Thu, 25 Apr 2002 05:41:37 +0900 Sender: emacs-devel-admin@gnu.org Message-ID: References: <8296-Wed24Apr2002190326+0300-eliz@is.elta.co.il> <200204241919.g3OJJ3104590@shade.twinsun.com> <200204242021.g3OKLS704607@shade.twinsun.com> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1019680978 6017 127.0.0.1 (24 Apr 2002 20:42:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2002 20:42:58 +0000 (UTC) Cc: emacs-devel@gnu.org, knagano@sodan.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 170TbO-0001Yw-00 for ; Wed, 24 Apr 2002 22:42:58 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 170TdE-0004j6-00 for ; Wed, 24 Apr 2002 22:44:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170TbJ-00074t-00; Wed, 24 Apr 2002 16:42:53 -0400 Original-Received: from meadow.scphys.kyoto-u.ac.jp ([130.54.54.165]) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 170Ta7-00070S-00 for ; Wed, 24 Apr 2002 16:41:40 -0400 Original-Received: (qmail 7532 invoked from network); 24 Apr 2002 20:40:53 -0000 Original-Received: from meadow.meadow.scphys.kyoto-u.ac.jp (HELO MILCH.meadowy.org.meadowy.org) (root@172.16.1.1) by meadow.meadow.scphys.kyoto-u.ac.jp with SMTP; 24 Apr 2002 20:40:53 -0000 Original-To: Paul Eggert In-Reply-To: <200204242021.g3OKLS704607@shade.twinsun.com> (Paul Eggert's message of "Wed, 24 Apr 2002 13:21:28 -0700 (PDT)") Original-Lines: 52 User-Agent: T-gnus/6.15.4 (based on Oort Gnus v0.04) (revision 11) SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/21.1 (i386-msvc-nt5.1.2600) MULE/5.0 (SAKAKI) Meadow/1.99 Alpha1 (AWOFUCHI) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:3218 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:3218 Paul Eggert writes: > Yes, in this case, Emacs will use PWD rather than the name you > specified to the non-POSIX shell. But this also happens on Unix > platforms with non-POSIX shells. It is not a problem that is specific > to Windows. And once we fix the bug in w32.c it will not be that > serious a problem, since Windows Emacs will act like GNU/Linux or Unix > Emacs in this situation. I can't understand why you stick to "PWD" environment variable on Windows. The information almost all of the application dose not set is so important? On Unix, shell and lots of programs usually put "nicer" pathname to "PWD". On Windows, most programs put "nicer" pathname to Get/SetCurrentDirectory(). Could you agree on this simple statement? Otherwise, would you really make convenience for few applications that set "PWD". To make matters worse, because of such applications, "PWD" may has wrong value, thus it may make displeasing inconvenience for most applications that don't set "PWD". >> > On Unix, most applications don't use $PWD; they use the working >> > directory. The only applications that set and use $PWD are those >> > that care about using a "nice" name for the working directory. >> >> I disagree on it. According to my knowledge, lots of Unix applications >> use "PWD". > > Some do, but most don't. For example, GNU 'tar' doesn't, even though > it uses getcwd (in order to implement the -C option). > >> Almost all of shells set "PWD" properly. But on Windows, even >> the standard shell program, "cmd.exe" dose not set "PWD". > > On Solaris 8, the standard shell program /bin/sh is not a POSIX shell, > and it does not set PWD. The situations are analogous. I still don't > see why Windows should be treated differently. And then, why do you use getcwd() instead of "PWD" on Unix? It's because getcwd() normalize pathname, and it's incovenient for many users, isn't it? But Windows never normalize pathname set by SetCurrentDirectory(). So users would not encounter the problem if we switch to use getcwd(). And I think it's more convenient on Windows. With regards, from himi