Re: "Pyrenean-pre8" problems on WinNT
- First Post
- Replies
- Stats
-
Go to
- ----- 2024 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2005 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2004 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2003 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2002 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2001 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2000 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1999 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 1998 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
Charles G Waldman <cgw(a)pgt.com> writes:
(1) (warning/warning) Error caught in
`make-auto-save-file-name':
Creating directory: No such file or directory, c:\home\cgw\home\cgw\/.autosave
(HOME is /home/cgw; this is apparently getting doubled up somehow)
It could be a bug in the NT expand-file-name routines (what does
(expand-file-name "test" "~/test/") give under your machines).
I do not know the NT port but shouldn't HOME be a directory including
driveletter since otherwise it is not uniquely specified?
The funny thing is that XEmacs tries to do its best to copy with funny
HOME values but on NT it seems to be switched of explicitly:
if (IS_DIRECTORY_SEP (nm[1])
|| nm[1] == 0) /* ~ by itself */
{
if (!(newdir = (Bufbyte *) get_home_directory()))
newdir = (Bufbyte *) "";
nm++;
#ifdef WINDOWSNT
collapse_newdir = 0;
#endif
}
The collapse_newdir explicitly tells XEmacs to not consider the fact your
HOME prefix starts with a / and just prepend the current dir which
happened to be c:\home\cgw in your case. It seems bogus to me.
Could you try removing that code and then test what happends to expand
file name in all case. i.e. with
1. HOME includes driveletter
2. HOME does not include drive letter.
3. HOME is a network path
Jan
Charles G Waldman
Wednesday, 2 December
Wed, 2 Dec
4:38 p.m.
New subject: "Pyrenean-pre8" problems on WinNT
Jan Vroonhof writes:
It could be a bug in the NT expand-file-name routines (what does
(expand-file-name "test" "~/test/") give under your machines).
(setenv "HOME" "/home/cgw")
(insert (getenv "HOME")) /home/cgw
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "C:\\home\\cgw")
(insert (getenv "HOME")) C:\home\cgw
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "\\\\reactor\\cgwhome")
(insert (getenv "HOME")) \\reactor\cgwhome
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "//reactor/cgwhome")
(insert (getenv "HOME")) //reactor/cgwhome
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
I do not know the NT port but shouldn't HOME be a directory
including
driveletter since otherwise it is not uniquely specified?
I tried it with HOME=/home/cgw and HOME=C:\home\cgw, get the same
behaviour (No such file or directory, c:\home\cgw\home\cgw\/.autosave)
both ways.
The funny thing is that XEmacs tries to do its best to copy with
funny
HOME values but on NT it seems to be switched of explicitly:
if (IS_DIRECTORY_SEP (nm[1])
|| nm[1] == 0) /* ~ by itself */
{
if (!(newdir = (Bufbyte *) get_home_directory()))
newdir = (Bufbyte *) "";
nm++;
#ifdef WINDOWSNT
collapse_newdir = 0;
#endif
}
The collapse_newdir explicitly tells XEmacs to not consider the fact your
HOME prefix starts with a / and just prepend the current dir which
happened to be c:\home\cgw in your case. It seems bogus to me.
Could you try removing that code and then test what happends to expand
file name in all case. i.e. with
1. HOME includes driveletter
2. HOME does not include drive letter.
3. HOME is a network path
Sorry, I was not completely clear on what code you wanted me to
remove. The 3 lines beginning with #ifdef WINDOWSNT, or the entire
block you quoted above? I tried it both ways.
With the "#ifdef WINDOWSNT" changed to "#ifdef XXXWINDOWSNTXXX"
I get no warnings from make-auto-save-file-name, but clearly wrong
behaviour from expand-file-name:
(setenv "HOME" "/home/cgw")
(insert (getenv "HOME")) /home/cgw
(insert (expand-file-name "test" "~/test/")) c:\test\test
(setenv "HOME" "C:\\home\\cgw")
(insert (getenv "HOME")) C:\home\cgw
(insert (expand-file-name "test" "~/test/")) c:\test\test
(setenv "HOME" "\\\\reactor\\cgwhome")
(insert (getenv "HOME")) \\reactor\cgwhome
(insert (expand-file-name "test" "~/test/")) c:\test\test
(setenv "HOME" "//reactor/cgwhome")
(insert (getenv "HOME")) //reactor/cgwhome
(insert (expand-file-name "test" "~/test/")) c:\test\test
With the entire block removed I get this result:
(setenv "HOME" "/home/cgw")
(insert (getenv "HOME")) /home/cgw
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "C:\\home\\cgw")
(insert (getenv "HOME")) C:\home\cgw
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "\\\\reactor\\cgwhome")
(insert (getenv "HOME")) \\reactor\cgwhome
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(setenv "HOME" "//reactor/cgwhome")
(insert (getenv "HOME")) //reactor/cgwhome
(insert (expand-file-name "test" "~/test/")) c:\home\cgw\test\test
(1) (warning/warning) Error caught in `make-auto-save-file-name':
Creating directory: Invalid argument, c:\home\cgw\½/.autosave
(2) (warning/warning) Error caught in `make-auto-save-file-name':
Creating directory: Invalid argument, c:\home\cgw\p»/.autosave
9487
days inactive
9487
days old
1 comments
2 participants
tags (0)
participants (2)
-
Charles G Waldman -
Jan Vroonhof