Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<5.0.2.1.2.20010302095419.034e5b60@ks.teknowledge.com>
X-Sender:	rschulz AT ks DOT teknowledge DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 5.0.2
Date:	Fri, 02 Mar 2001 09:58:52 -0800
To:	Tony Richardson <richardson AT evansville DOT edu>, harry DOT erwin AT sunderland DOT ac DOT uk,
	cygwin AT cygwin DOT com
From:	Randall R Schulz <rschulz AT teknowledge DOT com>
Subject:	RE: NT Problems
In-Reply-To:	<20010302.17242373@ar63pc.cecs.evansville.edu>
Mime-Version:	1.0

Tony,

BASH only writes its history when it's exiting, not after each command is 
executed.

In fact, you can inhibit BASH's history saving by clicking the close box of 
a window running BASH. I'm only hypothesizing from the empirical facts, but 
I suspect doing this terminates BASH in an abortive manner that prevents it 
from writing its .bash_history file.

Randall Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 09:24 3/2/2001, Tony Richardson wrote:
>I wonder if it might not be related to bash
>trying to write to it's history file in their
>home directory (which I'm assuming is still on
>the C: drive). Modify /etc/profile to change the
>value of HOME to be on the network drive before
>the user gets a prompt (or try setting HOME
>immediately)
>
>I use a network drive for my HOME, without any
>problems, so I know it can be done.
>
>Tony Richardson


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -