RE: [h-e-w] cygwin supbrocess startup directory

[Chris McMahan]

I don't see that as a risky scheme at all... I've been doing just that
for some time.

What you might try is to place a .emacs and .bashrc in the home
directory (c:/) that merely loads the actual code located wherever you
want. That's the type of thing I do with my .emacs. I set some global
configuration options (font, size, etc), then load the configuration
files located elsewhere.

This would minimize your percieved risk somewhat.

 -Chris

Scott, Steven writes:
>It seems like that would mess up one of my favorite shortcuts:  C-x C-f
>~/.emacs, because when it first starts up emacs assumes HOME is c:/
>The other alternative is to set HOME using windows environment variables.
>Then I could put .emacs and .bashrc in my cygwin HOME.  That's a risky
>solution though, b/c windows sometimes writes to the HOME directory.  
>
>-----Original Message-----
>From: Richard M. Heiberger [mailto:address@hidden
>Sent: Monday, February 11, 2002 2:18 PM
>To: 'address@hidden '; ''address@hidden' '; 'Underwood,
>Jonathan '; Scott, Steven
>Subject: RE: [h-e-w] cygwin supbrocess startup directory
>
>
>I suggest you tell emacs where your real HOME is by
>adding a line to .emacs
>
>(setenv "HOME" "c:/put/your/path/here")
>
>

-- 
    ================================
    Chris McMahan | address@hidden
    ================================