$HOME var

$HOME var

[Anthony G]

Hello,

I have a minor problem with Emacs for windows. Emacs works great on my Linux system at home, but at College where I spend a considerable amount of time coding, I have to use windows 2000.
The problem is as follows; Windows environment variables are set & locked on login. I can't add or change them, and command.exe is locked out. $HOME, for some FUBAR reason, is set to C:\, yet I don't have write permission FOR C:\. This means when I'm halfway through editing a file, emacs tries to save '.emacs.d' (or similar) to C: every microsecond. It doesn't hang, but It's so occupied in saving the file, that I need to enter commands quickly. I can't disable it in .emacs, because I can't save anything to $HOME (C:\), including .emacs.
Can I change $HOME in the emacs lisp files, or even an argument?

I'm an *ex* vim user, and enjoy learning emacs, but not being able to use emacs instead of the lame IDE that comes with the College's Java package, is a problem that needs to be resolved.


Thanks,

/Tony

RE: $HOME var

[Victor Kirk]

> The problem is as follows; Windows environment variables are 
> set & locked on login. I can't add or change them, and 
> command.exe is locked out. $HOME, for some FUBAR reason, is 
> set to C:\, yet I don't have write permission FOR C:\.

you could alway run emacs from a batch file and set %HOME% before
emcs executes, emacs will inherit the HOME variable from there, e.g.

set HOME=d:\mydir
runemacs

> Can I change $HOME in the emacs lisp files, or even an argument?

M-x apropos setenv

Vic
--

This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.

Re: $HOME var

[Torsten Müller]

Anthony G wrote:

> The problem is as follows; Windows environment variables are set &
> locked on login. I can't add or change them, and command.exe is
> locked out.

This is not correct. Surely you can set user specific environment
variables. There's a page in the "System" dialog of the Windows Control
Panel. After setting your variables you must log off and on again, and
then they are working.

T.M.

Re: $HOME var

[Bijan Soleymani]

Torsten Müller <Homunkulus@gmx.net> writes:

> Anthony G wrote:
> 
> > The problem is as follows; Windows environment variables are set &
> > locked on login. I can't add or change them, and command.exe is
> > locked out.
> 
> This is not correct. Surely you can set user specific environment
> variables. There's a page in the "System" dialog of the Windows Control
> Panel. After setting your variables you must log off and on again, and
> then they are working.

At my school this part of the control panel is blocked. I don't know
about his school but I would assume the same. The best way to get
around this is make a batch file as follows:
set HOME=c:\directory\that\i\want
set PATH=%PATH%;c:\emacs_directory\bin\
runemacs.exe

Basically have the first line set your home.
Have the second set your path to include emacs.
Then just have it run emacs.

P.S. Your school is evil for making you use Windows :)

Hope that helps,
Bijan

Re: $HOME var

[Bijan Soleymani]

Anthony G <goggs@bur.st> writes:

> Hello,
> 
> I have a minor problem with Emacs for windows. Emacs works great on my Linux system at home, but at College where I spend a considerable amount of time coding, I have to use windows 2000.
> The problem is as follows; Windows environment variables are set & locked on login. I can't add or change them, and command.exe is locked out. $HOME, for some FUBAR reason, is set to C:\, yet I don't have write permission FOR C:\. This means when I'm halfway through editing a file, emacs tries to save '.emacs.d' (or similar) to C: every microsecond. It doesn't hang, but It's so occupied in saving the file, that I need to enter commands quickly. I can't disable it in .emacs, because I can't save anything to $HOME (C:\), including .emacs.
> Can I change $HOME in the emacs lisp files, or even an argument?
make a batch file as follows:
set HOME=X:\directory\that\i\want       (where X is the drive you want)
set PATH=%PATH%;c:\emacs_directory\bin\ (or wherever emacs is)
runemacs.exe                            (or whatever executable runs emacs)

call it emacs.bat and put it on your desktop or wherever.

Basically have the first line set your home.
Have the second set your path to include emacs.
Then just have it run emacs.

P.S. Your school is evil for making you use Windows :)

Hope that helps,
Bijan

Re: $HOME var

[Chris McMahan]

Why not set the environment variables from within emacs? This won't
help you load the .emacs file itself, but you can modify the icon with
which you launch emacs to load that file as a command-line switch.

runemacs.exe -l <path to your .emacs file>

within your .emacs, use the format to set the environment variables:

(setenv "VARIABLE"  "value")

So to set your HOME variable from within emacs,
(setenv "HOME" "c:/documents\ and\ settings/username")


I may be completely missing something here, because I'm pretty heavily
embroiled into the cygwin environment on XP.

 - Chris

Anthony G <goggs@bur.st> writes:

> Hello,
> 
> I have a minor problem with Emacs for windows. Emacs works great on
> my Linux system at home, but at College where I spend a considerable
> amount of time coding, I have to use windows 2000.  The problem is
> as follows; Windows environment variables are set & locked on
> login. I can't add or change them, and command.exe is locked
> out. $HOME, for some FUBAR reason, is set to C:\, yet I don't have
> write permission FOR C:\. This means when I'm halfway through
> editing a file, emacs tries to save '.emacs.d' (or similar) to C:
> every microsecond. It doesn't hang, but It's so occupied in saving
> the file, that I need to enter commands quickly. I can't disable it
> in .emacs, because I can't save anything to $HOME (C:\), including
> .emacs.  Can I change $HOME in the emacs lisp files, or even an
> argument?
> 
> I'm an *ex* vim user, and enjoy learning emacs, but not being able
> to use emacs instead of the lame IDE that comes with the College's
> Java package, is a problem that needs to be resolved.
> 
> 
> Thanks,
> 
> /Tony
> 
> 

-- 
     (.   .)
  =ooO=(_)=Ooo========================
  Chris McMahan | cmcmahan-AT-one.net
  ====================================

Re: $HOME var

[Eli Zaretskii]

> From: Chris McMahan <cmcmahan+n@one.net>
> Newsgroups: gnu.emacs.help
> Date: 07 Mar 2003 16:38:33 -0500
> 
> So to set your HOME variable from within emacs,
> (setenv "HOME" "c:/documents\ and\ settings/username")

I don't recomment this: it creates a dangerous disparity between the
environment used by Emacs and the environment passed by Emacs to its
subprocesses.  In the archives of this thread, you will find many
examples of trouble into which this could get unsuspecting users.

Re: $HOME var

[Kevin Rodgers]

Eli Zaretskii wrote:

>>From: Chris McMahan <cmcmahan+n@one.net>
>>Newsgroups: gnu.emacs.help
>>Date: 07 Mar 2003 16:38:33 -0500
>>
>>So to set your HOME variable from within emacs,
>>(setenv "HOME" "c:/documents\ and\ settings/username")
>>
> 
> I don't recomment this: it creates a dangerous disparity between the
> environment used by Emacs and the environment passed by Emacs to its
> subprocesses.  In the archives of this thread, you will find many
> examples of trouble into which this could get unsuspecting users.

How could that be?  setenv updates process-environment, which is the environment
passed to subprocesses -- isn't it?

-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>

Re: $HOME var

[Eli Zaretskii]

> From: Kevin Rodgers <kevin.rodgers@ihs.com>
> Newsgroups: gnu.emacs.help
> Date: Mon, 10 Mar 2003 12:07:35 -0700
> > 
> > I don't recomment this: it creates a dangerous disparity between the
> > environment used by Emacs and the environment passed by Emacs to its
> > subprocesses.  In the archives of this thread, you will find many
> > examples of trouble into which this could get unsuspecting users.
> 
> How could that be?  setenv updates process-environment, which is the environment
> passed to subprocesses -- isn't it?

Yes.  But the environment used by Emacs itself is unaffected by
setenv.