Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<19990524032140.20995.rocketmail@web807.mail.yahoo.com>
Date:	Sun, 23 May 1999 20:21:40 -0700 (PDT)
From:	Rick Rankin <rick_rankin AT yahoo DOT com>
Subject:	Re: bash history not restored
To:	Ian Zimmerman <itz AT lbin DOT com>, earnie_boyd AT yahoo DOT com,
	cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0

--- Ian Zimmerman <itz AT lbin DOT com> wrote:
> Earnie Boyd wrote:
> > 
> > --- Victor Ott <vott AT frank DOT de> wrote:
> > > Ian Zimmerman wrote:
> > > > No matter what I do, I can't seem to make bash restore the command
> > > > history from .bash_history when it starts.  During a session,
> > > > interactive history mode works; moreover, current history is saved to
> > > > the file when session ends.  But the next session will again start with
> > > > empty history :-[
> > > >
> > > > Running Cygwin-b20.1, NT Workstation SP4, FAT fs, text mount.
> > >
> > > I think it's the text mount. As far I've seen, bash imports history
> > > entries from past bash sessions only when 'binmode' is set in CYGWIN
> > > env. var., and that's what I am doing. Others might have other
> > > solutions.
> > 
> > Hmm.  It is noted in the FAQ or documentation however that specifying the
> > [no]binmode value causes other problems and the suggestion is to not set
> this
> > switch in the CYGWIN variable.  The problem is particular to specifying the
> > file processing mode in the open/fopen statements.  I believe this was
> fixed
> > and downloading the Jan 15th snapshot would solve the FAQ stated problem.
> 
> So, HOW do I make history work AND have text opens/fopens by default? 
> Is this a lose/lose situation?  After all, text mount is still the
> default behavior, so this would make history not work out of the box. 
> (I can't test that because my setup has gotten too far outside the box.
> :)
> 
> Text mount is absolutely necessary for me; without it, I can't use Emacs
> (or any other Cygwin program) to handle non-Cygwin originated files.
> 

I don't understand this comment. Even though I'm currently using only text
mounts, I used binary mounts for quite a while.  I've used both NT Emacs and
XEmacs (Cygwin build) successfully on both, editing cygwin and non-cygwin
generated text files. Can you provide more specifics?

> -- 
> Ian Zimmerman
> Lightbinders, Inc.
> 2325 3rd Street #324, San Francisco, California 94107
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 

Rick
--
Rick Rankin
rick_rankin AT yahoo DOT com

_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -