From: Stephen Leake <stephen_leake@member.fsf.org>
Cc: Stephen Leake <stephen_leake@member.fsf.org>,
emacs-devel@gnu.org, drew.adams@oracle.com, miles@gnu.org
Subject: Re: abbreviate-file-name on Windows seems incorrect
Date: Mon, 08 Jan 2007 03:44:09 -0500 [thread overview]
Message-ID: <u7ivxewme.fsf@member.fsf.org> (raw)
In-Reply-To: <uodpaimy7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 07 Jan 2007 22:47:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Please show your precise test case (in "emacs -Q").
On trying to reproduce my test, I'm getting different results (sigh).
Here's the test:
On Windows, before Emacs, in Cygwin bash:
$ echo $HOME
/Stephe
$ emacs -Q
---- in *scratch* -------
(getenv "HOME")
"C:\\Stephe"
(expand-file-name "~/foo")
"c:/Stephe/foo"
(abbreviate-file-name "/Stephe/foo")
"/Stephe/foo"
(abbreviate-file-name "c:\\Stephe\\foo")
"c:\\Stephe\\foo"
(abbreviate-file-name "c:\\Projects\\foo")
"c:\\Projects\\foo"
(setenv "HOME" "c:\\Projects")
"c:\\Projects"
(getenv "HOME")
"c:\\Projects"
(expand-file-name "~/foo")
"c:/Projects/foo"
(abbreviate-file-name "c:\\Projects\\foo")
"c:\\Projects\\foo"
----------
Now I'm getting the expected behavior from 'expand-file-name', but not
from 'abbreviate-file-name'. This is from
GNU Emacs 22.0.92.1 (i386-mingw-nt5.1.2600) of 2007-01-06 on ACS1100007992
I have access to a Sun Solaris box:
GNU Emacs 21.4.1 (sparc-sun-solaris2.8, X toolkit, Xaw3d scroll bars) of 2005-09-21 on ra
-------
(getenv "HOME")
"/home/stephe"
(expand-file-name "~/foo")
"/home/stephe/foo"
(abbreviate-file-name "/home/stephe/foo")
"~/foo"
(abbreviate-file-name "/home/Projects/foo")
"/home/Projects/foo"
(setenv "HOME" "/home/Projects")
t
(getenv "HOME")
"/home/Projects"
(expand-file-name "~/foo")
"/home/Projects/foo"
(abbreviate-file-name "/home/Projects/foo")
"/home/Projects/foo"
---------
This is exhibiting the expected behavior for 'expand-file-name', and
the caching behavior for 'abbreviate-file-name'.
--
-- Stephe
next prev parent reply other threads:[~2007-01-08 8:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 7:56 abbreviate-file-name on Windows seems incorrect Drew Adams
2007-01-06 11:37 ` Lennart Borgman (gmail)
2007-01-06 14:18 ` Eli Zaretskii
2007-01-06 15:03 ` Lennart Borgman (gmail)
2007-01-06 11:56 ` Eli Zaretskii
2007-01-06 16:22 ` Drew Adams
2007-01-06 21:51 ` Eli Zaretskii
2007-01-06 22:42 ` Drew Adams
2007-01-07 2:44 ` Miles Bader
2007-01-07 4:12 ` Eli Zaretskii
2007-01-07 14:29 ` Stephen Leake
2007-01-07 20:47 ` Eli Zaretskii
2007-01-07 22:03 ` Drew Adams
2007-01-07 22:08 ` Drew Adams
2007-01-08 1:40 ` Chris Moore
2007-01-08 2:04 ` Drew Adams
2007-01-08 10:15 ` Jason Rumney
2007-01-08 16:29 ` Drew Adams
2007-01-09 0:01 ` Richard Stallman
2007-01-09 0:30 ` Jason Rumney
2007-01-09 12:55 ` Stephen Leake
2007-01-09 17:57 ` Richard Stallman
2007-01-08 8:44 ` Stephen Leake [this message]
2007-01-08 13:07 ` Chris Moore
2007-01-08 19:30 ` Eli Zaretskii
2007-01-09 12:52 ` Stephen Leake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u7ivxewme.fsf@member.fsf.org \
--to=stephen_leake@member.fsf.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=miles@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.