3:46 a.m.
================================================================
Dear Bug Team!
On Windows XP, I'm unable to open files in common directories like
"~/My Documents". If I had to guess, the problem is with filenames
that contain spaces. This seems like pretty basic stuff however
I just installed XEmacs and I don't have a .xemacs file.
Hope there's an easy answer!
- Hans (Hans.Muller(a)sun.com <mailto:Hans.Muller＠sun.com>)
================================================================
System Info to help track down your bug:
---------------------------------------
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.4.19 "Constant Variable" configured for `i586-pc-win32'.
Building XEmacs in
"e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4-2006-01-28\\nt".
Using compiler "cl -nologo -W3 -O2 -G5 -MD".
Installing XEmacs in "c:\\XEmacs-built\\XEmacs-21.4.19".
Package path is
"~\\.xemacs;;c:\\XEmacs-built\\site-packages;c:\\XEmacs-built\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library
Load-Path Lisp Shadows:
----------------------
nil
Installed XEmacs Packages:
-------------------------
(xemacs-devel ver: 1.72 upstream: No-Upstream-Ver)
(xemacs-base ver: 2.01 upstream: No-Upstream-Ver)
(time ver: 1.14 upstream: 1.17)
(text-modes ver: 1.9 upstream: No-Upstream-Ver)
(texinfo ver: 1.3 upstream: No-Upstream-Ver)
(speedbar ver: 1.28 upstream: 0.14beta4)
(sounds-wav ver: 1.12 upstream: No-Upstream-Ver)
(sh-script ver: 1.21 upstream: 2.0f)
(semantic ver: 1.19 upstream: 1.4.2)
(prog-modes ver: 2.06 upstream: No-Upstream-Ver)
(perl-modes ver: 1.08 upstream: No-Upstream-Ver)
(pc ver: 1.28 upstream: No-Upstream-Ver)
(os-utils ver: 1.36 upstream: No-Upstream-Ver)
(net-utils ver: 1.48 upstream: N/A)
(mail-lib ver: 1.75 upstream: No-Upstream-Ver)
(fsf-compat ver: 1.15 upstream: No-Upstream-Ver)
(eieio ver: 1.05 upstream: 0.17)
(efs ver: 1.33 upstream: 1.23)
(edit-utils ver: 2.32 upstream: No-Upstream-Ver)
(ediff ver: 1.6 upstream: 2.75)
(edebug ver: 1.21 upstream: No-Upstream-Ver)
(ecb ver: 1.22 upstream: 2.31)
(dired ver: 1.17 upstream: 7.13)
(debug ver: 1.17 upstream: No-Upstream-Ver)
(cc-mode ver: 1.45 upstream: 5.30.10)
(c-support ver: 1.22 upstream: No-Upstream-Ver)
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 cc-mode cc-menus
cc-cmds cc-styles cc-align cc-engine cc-vars cc-defs regexp-opt efs-cu
shell comint ring xemacs-devel-autoloads xemacs-base-autoloads
time-autoloads text-modes-autoloads texinfo-autoloads
speedbar-autoloads sounds-wav-autoloads sh-script-autoloads
semantic-autoloads prog-modes-autoloads perl-modes-autoloads
pc-autoloads os-utils-autoloads net-utils-autoloads mail-lib-autoloads
fsf-compat-autoloads eieio-autoloads efs-autoloads
edit-utils-autoloads ediff-autoloads edebug-autoloads ecb-autoloads
dired-autoloads debug-autoloads cc-mode-autoloads c-support-autoloads
lisp-autoloads loadhist auto-show fontl-hooks code-cmds gutter-items
menubar-items x-menubar dragdrop mode-motion mouse itimer auto-save
lisp-mode easymenu iso8859-1 page buff-menu lib-complete help-nomule
cus-file derived frame text-props obsolete cus-start custom widget
cl-extra mini-cl cl cl-19 packages backquote very-early-lisp
file-coding mswindows-scrollbars mswindows toolbar native-sound
scrollbar network-streams subprocesses menu-accelerator-support
menubar md5 xemacs gutter tiff png gif jpeg xpm xbm lisp-float-type
windows-nt dragdrop-api dialog devices window-system base64)
Recent keystrokes:
-----------------
v a c SPC I m a g e I n f o . j a v a RET c : \ p r
o TAB C-a C-k RET C-x C-f p r o TAB j a v TAB ? j d
k TAB BS BS r e TAB C-g button1 button1up C-x C-f D
o TAB ? h a n TAB ? < y TAB BS BS M y TAB t e s t .
t x t RET C-x C-q RET C-x C-s button1 button1up ESC
x r e p o r t TAB x e TAB RET
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
Directory c:\Documents and Settings\hans\My Documents\ write-protected
File not found and directory write-protected
Making completion list...
Making completion list...
Quit
Making completion list...
No completions of C:\>c:\pro
Completing file name...
c:\
Wrote c:\ImageInfo.java
(New file)
File not found and directory write-protected
Making completion list...
Making completion list...
Quit
Quit
Quit
Making completion list...
5:30 a.m.
>>>> "Hans" == Hans Muller
<Hans.Muller(a)Sun.COM> writes:
Hans> On Windows XP, I'm unable to open files in common
Hans> directories like "~/My Documents". If I had to guess, the
Hans> problem is with filenames that contain spaces.
How are you opening them? With C-x C-f, or with the Open File Dialog?
Where exactly do you run into a problem?
With C-x C-f, as far as I know quoting the space with C-q should allow
you to enter it in the minibuffer, and that should be sufficient to
open the file. (Works for me on Linux for a file name.) Also, if "My
Documents" is the only file or directory whose name begins with "My",
then M y TAB will complete correctly, and you can open it that way.
(Works for me on Linux for a file name.)
With the Open File dialog, just click on the file or directory name.
(Works for me on Linux for a file name.)
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
4:14 p.m.
Thanks for the response. I left for vacation shortly after sending the
problem
report so this is a rather belated reply:
Stephen J. Turnbull wrote:
>>>>> "Hans" == Hans Muller
<Hans.Muller(a)Sun.COM> writes:
>>>>>
Hans> On Windows XP, I'm unable to open files in common
Hans> directories like "~/My Documents". If I had to guess, the
Hans> problem is with filenames that contain spaces.
How are you opening them? With C-x C-f, or with the Open File Dialog?
Where exactly do you run into a problem?
Either approach for opening a file fails. I've found that opening
"~/My
Documents" in dired, and
then creating a new subdirectory (with "+") and then opening a files in
the subdir, does work.
Maybe the problem (on XP) has to do with paths whose directory component
ends with a name that contains a space?
With C-x C-f, as far as I know quoting the space with C-q should
allow
you to enter it in the minibuffer, and that should be sufficient to
open the file. (Works for me on Linux for a file name.)
Doesn't work on XP.
Result is: "File not found and directory write
protected".
Also, if "My
Documents" is the only file or directory whose name begins with "My",
then M y TAB will complete correctly, and you can open it that way.
(Works for me on Linux for a file name.)
Tab completion definitely works, however the result is always the same:
"File not found and
directory write protected".
With the Open File dialog, just click on the file or directory name.
(Works for me on Linux for a file name.)
I hadn't tried that, however it doesn't work. Results are the same.
- Hans
5:26 p.m.
On 7/13/06, Hans Muller <Hans.Muller(a)sun.com> wrote:
Thanks for the response. I left for vacation shortly after sending the
problem
report so this is a rather belated reply:
Stephen J. Turnbull wrote:
>>>>>> "Hans" == Hans Muller <Hans.Muller(a)Sun.COM>
writes:
>>>>>>
>
> Hans> On Windows XP, I'm unable to open files in common
> Hans> directories like "~/My Documents". If I had to guess, the
> Hans> problem is with filenames that contain spaces.
>
> How are you opening them? With C-x C-f, or with the Open File Dialog?
> Where exactly do you run into a problem?
>
Either approach for opening a file fails. I've found that opening "~/My
Documents" in dired, and
then creating a new subdirectory (with "+") and then opening a files in
the subdir, does work.
Maybe the problem (on XP) has to do with paths whose directory component
ends with a name that contains a space?
> With C-x C-f, as far as I know quoting the space with C-q should allow
> you to enter it in the minibuffer, and that should be sufficient to
> open the file. (Works for me on Linux for a file name.)
Doesn't work on XP. Result is: "File not found and directory write
protected".
This Just Works For Me with either a cygwin or native build with a
recent 21.4.19 build. Is your HOME environment variable set
explicitly? Mine is set to e:/acs, but I bet in your case, ~ expands
to a name with a space in it (probably c:\Documents and
Settings\hans). My guess is that expanding the home directory needs
to be quoted somehow. What does this evaluate to:
(getenv "HOME")
Does this work:
C-x C-f c:\Documents and Settings\hans\My Documents\foo.txt
Another experiment I'd like you to try, please, is to:
(setq debug-on-error t)
C-x C-f ~/My Documents/foo.txt
and please send the backtrace to xemacs-beta.
Thanks,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
4:54 a.m.
Sorry to be glacial. It's been a busy summer :-). Here's the feedback
you asked for ...
Vin Shelton wrote:
On 7/13/06, Hans Muller <Hans.Muller(a)sun.com> wrote:
>
> Thanks for the response. I left for vacation shortly after sending the
> problem
> report so this is a rather belated reply:
>
> Stephen J. Turnbull wrote:
> >>>>>> "Hans" == Hans Muller <Hans.Muller(a)Sun.COM>
writes:
> >>>>>>
> >
> > Hans> On Windows XP, I'm unable to open files in common
> > Hans> directories like "~/My Documents". If I had to guess,
the
> > Hans> problem is with filenames that contain spaces.
> >
> > How are you opening them? With C-x C-f, or with the Open File Dialog?
> > Where exactly do you run into a problem?
> >
> Either approach for opening a file fails. I've found that opening "~/My
> Documents" in dired, and
> then creating a new subdirectory (with "+") and then opening a files in
> the subdir, does work.
> Maybe the problem (on XP) has to do with paths whose directory component
> ends with a name that contains a space?
> > With C-x C-f, as far as I know quoting the space with C-q should allow
> > you to enter it in the minibuffer, and that should be sufficient to
> > open the file. (Works for me on Linux for a file name.)
> Doesn't work on XP. Result is: "File not found and directory write
> protected".
This Just Works For Me with either a cygwin or native build with a
recent 21.4.19 build. Is your HOME environment variable set
explicitly?
It's not set at all. I started with a pretty vanilla XP
installation,
downloaded
and installed XEmacs, and didn't create any .foo config files.
Mine is set to e:/acs, but I bet in your case, ~ expands
to a name with a space in it (probably c:\Documents and
Settings\hans). My guess is that expanding the home directory needs
to be quoted somehow. What does this evaluate to:
(getenv "HOME")
nil
Does this work:
C-x C-f c:\Documents and Settings\hans\My Documents\foo.txt
No; that just
generates "file not found and directory write protected".
Another experiment I'd like you to try, please, is to:
(setq debug-on-error t)
C-x C-f ~/My Documents/foo.txt
and please send the backtrace to xemacs-beta.
That doesn't generate a
backtrace. Emacs just creates a read-only
buffer called
foo.txt that points to the specified path. Same for this:
(setq debug-on-error t)
t
(find-file " ~/My Documents/foo.txt")
#<buffer "foo.txt">
I also get the same results for:
(find-file "c:\\Documents and Settings\\hans\\My Documents\\foo.txt") and
(find-file "c:/Documents and Settings/hans/My Documents/foo.txt")
If a setenv HOME to the ...\hans\My Documents path, then C-x C-f does work.
I've create a ~/.xemacs file that contains the following, and now all seems
copacetic:
(setenv "HOME" "c:\\Documents and Settings\\hans\\My Documents")
(message (concat "Loading " (getenv HOME) "\\.xemacs
<file://%5C%5C.xemacs>"))
I've been running XEmacs 21.4 (April 2001) on an XP machine for a year
or two
without having set the HOME env variable and did not see the problem
outlined
here.
Thanks for the help with this; I'm on the XEmacs road again.
- Hans
Thanks,
Vin
6493
days inactive
6514
days old
4 comments
3 participants
participants (3)
-
Hans Muller -
Stephen J. Turnbull -
Vin Shelton