1:59 p.m.
Some time ago, Hrvoje Niksic wrote...
|+
| Whatever we do, please note that (getenv "HOME") is definitely the
| Wrong Thing to do. We should create a `user-home-directory' function
| which would do the necessary magic of finding a system-specific home
| directory. All the places that use (getenv "HOME") should be fixed to
| use the new function.
|
| The suggestion comes from Ben.
I think the better approach under Windows is to have a place for
.emacs and stuff configurable.
[ using a setup program to initialize XEmacs's notion of $HOME. ]
Kirill
This would be great for the binary distribution, but we still have to
figure out what needs to be done when compiling from source.
And another thing, using (getenv "HOME") is probably the right thing to use
for `user-home-directory' under Cygwin32. BASH and TCSH both use
(getenv "HOME") to determine `~', so XEmacs should probably also...
Thanks, guys.
--
Paul Stodghill <stodghil(a)cs.cornell.edu>
http://www.cs.cornell.edu/stodghil/
6:18 p.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
Some time ago, Paul Stodghill wrote...
|+
| And another thing, using (getenv "HOME") is probably the right thing to use
| for `user-home-directory' under Cygwin32. BASH and TCSH both use
| (getenv "HOME") to determine `~', so XEmacs should probably also...
|-
I propose the following order of precedence:
Highest: Registry setting (when available).
2. HOME
3. HOMEDRIVE/HOMEPATH
Kirill
6:55 p.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
"Kirill M. Katsnelson" <kkm(a)kis.ru> wrote:
I propose the following order of precedence:
Highest: Registry setting (when available).
2. HOME
3. HOMEDRIVE/HOMEPATH
I just submitted some patches for this, but the precedence is (as
mentioned in the patch):
1. Existing value of $HOME
2. Registry setting
3. $HOMEDRIVE$HOMEPATH (under Win95/NT)
4. Under Win95/NT, the current directory. Under Unix, "/".
Yeah, this is questionable, but I wanted to get the patch out
ASAP, to get some feedback, and this could be fixed later.
-- Darryl Okahata
Internet: darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.
12:15 a.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
Kirill M. Katsnelson wrote:
Some time ago, Paul Stodghill wrote...
|+
| And another thing, using (getenv "HOME") is probably the right thing to use
| for `user-home-directory' under Cygwin32. BASH and TCSH both use
| (getenv "HOME") to determine `~', so XEmacs should probably also...
|-
I propose the following order of precedence:
Highest: Registry setting (when available).
2. HOME
3. HOMEDRIVE/HOMEPATH
I would have thought that HOME should be first, as I would presume
that it is easier to temporarily change the value of HOME than the
registry setting (I don't use Windows, so I don't know this for a
fact).
Also, it would seem (to me) sensible for ~ to mean the same thing to
both XEmacs and the shell in as many cases as possible.
--
Glynn Clements <glynn(a)sensei.co.uk>
5 p.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
-----Original Message-----
From: owner-xemacs-nt(a)xemacs.org [mailto:owner-xemacs-nt＠xemacs.org]On
Behalf Of Glynn Clements
Sent: Tuesday, May 26, 1998 4:16 PM
To: xemacs-beta(a)xemacs.org; xemacs-nt(a)xemacs.org
Subject: Re: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
Kirill M. Katsnelson wrote:
> Some time ago, Paul Stodghill wrote...
> |+
> | And another thing, using (getenv "HOME") is probably the
right thing to use
> | for `user-home-directory' under Cygwin32. BASH and TCSH both use
> | (getenv "HOME") to determine `~', so XEmacs should probably
also...
> |-
>
> I propose the following order of precedence:
> Highest: Registry setting (when available).
> 2. HOME
> 3. HOMEDRIVE/HOMEPATH
I would have thought that HOME should be first, as I would presume
that it is easier to temporarily change the value of HOME than the
registry setting (I don't use Windows, so I don't know this for a
fact).
Debatable. Using the registry has the advantage that any change is immediate
and permanent without logging off/on or rebooting. It has the disadvantage
that editing the registry can be very dangerous if you don't know what
you're doing.
I'm aware of programs that have taken one path or the other. In each case,
users get confused. I think I prefer having the registry take precedence,
but only if, for the faint of heart, there's a simple mechanism for setting
the appropriate values without hand-editing the registry.
Also, it would seem (to me) sensible for ~ to mean the same thing to
both XEmacs and the shell in as many cases as possible.
A mechanism could be provided to set an environment variable from the
registry setting. For example,
bash: export HOME=$(getreg HOME)
cmd: getreg HOME HOME
--
Glynn Clements <glynn(a)sensei.co.uk>
Rick
begin 666 Rankin, Rick.vcf
M0D5'24XZ5D-!4D0-"E9%4E-)3TXZ,BXQ#0I..E)A;FMI;CM2:6-K#0I&3CI2
M86YK:6XL(%)I8VL-"D]21SI-;W1O<F]L82!#3E-3#0I4251,13I3<BX＠4W1A
M9F8＠16YG:6YE97(-"E1%3#M73U)+.U9/24-%.B＠V,#(I(#<S,BTS-#DT#0I4
M14P[5T]22SM&05＠Z*#8P,BD(a)-S,R+3(R,#4-"D%$4CM73U)+.T5.0T]$24Y'
M/5%53U1%1"U04DE.5$%"3$4Z.SLR-3 Q(%,N(%!R:6-E(%)D/3!$/3!!36%I
M;"!3=&]P($<Q,3 W.T-H86YD;&5R.T%:.S＠U,C0X.U4N4RY!+＠T*3$%"14P[
M5T]22SM%3D-/1$E.1SU154]4140M4%))3E1!0DQ%.C(U,#$＠4RX＠4')I8V4＠
M4F0],$0],$%-86EL(%-T;W ＠1S$Q,#<],$0],$%#:&%N9&QE<BP＠05H＠.#4R
M-#＠],$0],$%5+E,N02X-"D5-04E,.U!2148[24Y415).150Z4FEC:U]286YK
M:6Y0,34R-31 96UA:6PN;6]T+F-O;0T*4D56.C$Y.3＠P-#$V5#$V,3$U,UH-
,"D5.1#I60T%21 T*
`
end
1:46 a.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
Rick Rankin wrote:
> > |+
> > | And another thing, using (getenv "HOME") is probably the right
thing to use
> > | for `user-home-directory' under Cygwin32. BASH and TCSH both use
> > | (getenv "HOME") to determine `~', so XEmacs should probably
also...
> > |-
> >
> > I propose the following order of precedence:
> > Highest: Registry setting (when available).
> > 2. HOME
> > 3. HOMEDRIVE/HOMEPATH
>
> I would have thought that HOME should be first, as I would presume
> that it is easier to temporarily change the value of HOME than the
> registry setting (I don't use Windows, so I don't know this for a
> fact).
Debatable. Using the registry has the advantage that any change is immediate
and permanent without logging off/on or rebooting. It has the disadvantage
that editing the registry can be very dangerous if you don't know what
you're doing.
I'm aware of programs that have taken one path or the other. In each case,
users get confused. I think I prefer having the registry take precedence,
but only if, for the faint of heart, there's a simple mechanism for setting
the appropriate values without hand-editing the registry.
> Also, it would seem (to me) sensible for ~ to mean the same thing to
> both XEmacs and the shell in as many cases as possible.
A mechanism could be provided to set an environment variable from the
registry setting. For example,
bash: export HOME=$(getreg HOME)
cmd: getreg HOME HOME
The question is whether (shell-command "cat ~/foo") will show you the
same file as `C-x C-f ~/foo RET' when the registry's idea of the
user's home directory differs from what is contained in $HOME.
--
Glynn Clements <glynn(a)sensei.co.uk>
3:23 p.m.
New subject: 21.0 beta41, cygwin32, ~init-file-user doesn't work.
At 01:46 AM 5/28/98 +0100, Glynn Clements wrote:
The question is whether (shell-command "cat ~/foo") will
show you the
same file as `C-x C-f ~/foo RET' when the registry's idea of the
user's home directory differs from what is contained in $HOME.
Under cygwin I don't think the registry setting should have the highest
priority. bash doesn't use it and the problem is that you could have a
correctly set up bash and xemacs which both have different ideas about
HOME. The registry should be the fallback IMHO.
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
9675
days inactive
9677
days old
6 comments
6 participants
participants (6)
-
Andy Piper -
Darryl Okahata -
Glynn Clements -
Kirill M. Katsnelson -
Paul Stodghill -
Rick Rankin