I just noticed that my 'auto-save-hash-directory' variable is currently:
"e:\\home\\andyp\\.autosave\\hash\\"
And, I'm pretty sure that I didn't do that. Hi andy.
The value appears to be coming from the xemacs executable:
c:/PROGRA~1/XEMACS/XEMACS-21.4.3
i686-pc-cygwin/xemacs:...auto-save-hash-directory..../windows/home/andyp/.autosave/hash/...
I'm going to hazard a guess that the andy made the windows xemacs
releases and that his .emacs is getting into the build.
-jeff
Show replies by date
From: Jeff Mincy <jeff(a)delphioutpost.com>
Date: Sun, 23 Sep 2001 19:17:12 -0400
I just noticed that my 'auto-save-hash-directory' variable is currently:
"e:\\home\\andyp\\.autosave\\hash\\"
And, I'm pretty sure that I didn't do that. Hi andy.
The value appears to be coming from the xemacs executable:
c:/PROGRA~1/XEMACS/XEMACS-21.4.3
i686-pc-cygwin/xemacs:...auto-save-hash-directory..../windows/home/andyp/.autosave/hash/...
I'm going to hazard a guess that the andy made the windows xemacs
releases and that his .emacs is getting into the build.
Ummm, actually, I'm not using the cygwin version, I'm using the regular
windows build.
bash% fgrep andyp i586-pc-win32/xemacs.exe
e:\home\andyp\.autosave\hash\
early-packages..e:\home\andyp\.xemacs\
I don't think my prior guess is correct. I think this is happening
because of the explicit expand-file-name in the defvar. The
defvar should have a value of
"~/.autosave/hash/"
or
(concat (or auto-save-directory auto-save-directory-fallback) "hash/")
and should not expand the ~ file when building the executable.
(defvar auto-save-hash-directory
(expand-file-name "hash/" (or auto-save-directory
auto-save-directory-fallback))
"If non-nil, directory used for hashed autosave filenames.")
Also, I'm concerned about the
early-packages..e:\home\andyp\.xemacs\
-jeff