Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <1378.10.0.0.7.1095587788.squirrel@10.0.0.7>
In-Reply-To: <B9721831E371CD4F84C4F5E87476D356FB81BB@iu-mssg-mbx04.exchange.iu.edu>
References: <B9721831E371CD4F84C4F5E87476D356FB81BB AT iu-mssg-mbx04 DOT exchange DOT iu DOT edu>
Date: Sun, 19 Sep 2004 10:56:28 +0100 (BST)
Subject: Re: emacs problem results from bad $HOME value
From: "John Morrison" <john DOT r DOT morrison AT ntlworld DOT com>
To: cygwin AT cygwin DOT com
User-Agent: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-15
Content-Transfer-Encoding: 8bit

Sarah wrote:
> Solved the problem with emacs flaking out.  The default values for $HOME
> and $home set up in the default .login file were wrong.

Hi Sarah,

What .login file?  (what shell come to that?)

> Commented out
> the lines that set them and hardcoded the correct location.  Pretty

You might be better to modify the root - /etc/passwd, but I'm kinda
suprised it didn't work; what is the home specified in there and what
do you want it to be?

> irritating that this emacs (21.2-13) can't deal with this though. I've
> never had this problem with any emacs I've used before.  Should be able
> to say ^x^w and correct the pathname rather than being unable to
> continue working and unable to do anything to save one's work.  Is one
> of the other options more robust?

Can't help with the emac problem - I'm a vim person ;)

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/