2:30 a.m.
I am running Windows 95 and Cygwin 32 with coolview. I do
not use password protection and I have not created a unix type
passwd file. While poking into this I have found a couple of
things. I have setup a USER environment variable in my cyqwin.bat
file.
1. The variable init-file-user is set to the value of USER even
though I have not invoked xemacs with a "-u" command line option.
2. If I evaluate (expand-file-name (concat "~" init-file-user "/"))
I get /develop/xemacs-20/lisp/~dbush where the current buffer directory
is /develop/xemacs-20/lisp and USER=dbush.
If I (setq init-file-user "") and then evaluate (expand-file-name ...)
again I get the value of HOME as expected.
The question is where should this be fixed? The comments in fileio.c indicate
that ~foo and ~ should be equivalent if foo is the curent user - at least
in the Windows NT case. The other possibility is to modify the behavior
of init-file-user so it is set only if the -u option is used. I've
looked for other uses of init-file-user and don't see them, but I have
only a limited set of packages installed.
Please bear with these questins. I can figure out how to fix something
technicaly, but it is harder to get a good sense on integrating with
the ongoing development philosophy.
david
9:17 a.m.
At 09:30 PM 5/17/98 -0400, David Bush wrote:
The question is where should this be fixed? The comments in fileio.c
indicate
that ~foo and ~ should be equivalent if foo is the curent user - at
least
in the Windows NT case. The other possibility is to modify the behavior
of init-file-user so it is set only if the -u option is used. I've
looked for other uses of init-file-user and don't see them, but I have
only a limited set of packages installed.
Be aware that the cygwin version does not build with WINDOWSNT defined. If
there are things that need to be migrated to cygwin then there needs to be
a __CYGWIN32__ in there somewhere. A case in point is the path handling
code - the cygwin version currently doesn't grok drive letters or //foo/bar
type paths. I am undecided as to whethe this is a good thing or not. I
still prefer what we have to the way NTemacs operates in this area but
understanding // would be nice.
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp
2:46 p.m.
Andy Piper wrote:
At 09:30 PM 5/17/98 -0400, David Bush wrote:
>The question is where should this be fixed? The comments in fileio.c
indicate
>that ~foo and ~ should be equivalent if foo is the curent user - at least
>in the Windows NT case. The other possibility is to modify the behavior
>of init-file-user so it is set only if the -u option is used. I've
>looked for other uses of init-file-user and don't see them, but I have
>only a limited set of packages installed.
Be aware that the cygwin version does not build with WINDOWSNT defined. If
there are things that need to be migrated to cygwin then there needs to be
a __CYGWIN32__ in there somewhere. A case in point is the path handling
code - the cygwin version currently doesn't grok drive letters or //foo/bar
type paths. I am undecided as to whethe this is a good thing or not. I
still prefer what we have to the way NTemacs operates in this area but
understanding // would be nice.
It seems to be that the more flexibility the better. This also raises
the question of DOS style path separators. I'll look, but this may be
more of a 21.1 feature with that many changes. The home directory
problem does need fixing now.
Thanks for your comments, I'll see what I can do.
david
2:56 p.m.
At 09:46 AM 5/18/98 -0400, David Bush wrote:
Andy Piper wrote:
>
> At 09:30 PM 5/17/98 -0400, David Bush wrote:
> >The question is where should this be fixed? The comments in fileio.c
> indicate
> >that ~foo and ~ should be equivalent if foo is the curent user - at least
> >in the Windows NT case. The other possibility is to modify the behavior
> >of init-file-user so it is set only if the -u option is used. I've
> >looked for other uses of init-file-user and don't see them, but I have
> >only a limited set of packages installed.
>
> Be aware that the cygwin version does not build with WINDOWSNT defined. If
> there are things that need to be migrated to cygwin then there needs to be
> a __CYGWIN32__ in there somewhere. A case in point is the path handling
> code - the cygwin version currently doesn't grok drive letters or //foo/bar
> type paths. I am undecided as to whethe this is a good thing or not. I
> still prefer what we have to the way NTemacs operates in this area but
> understanding // would be nice.
It seems to be that the more flexibility the better. This also raises
the question of DOS style path separators. I'll look, but this may be
more of a 21.1 feature with that many changes.
I currently don't believe this should be supported under cygwin. cygwin
converts environment variables like HOME && PATH to unix style anyway. My
rule of thumb would be: if it works under cygwin bash then it should work
in xemacs. This means that drives and // should be understood but \ not.
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp
9686
days inactive
9686
days old
3 comments
2 participants
participants (2)
-
Andy Piper -
David Bush