Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bugreport zsh 3.1.2: Shell exits prematurely after aborting history-incremental-search-backward
- X-seq: zsh-workers 4096
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Bugreport zsh 3.1.2: Shell exits prematurely after aborting history-incremental-search-backward
- Date: Thu, 11 Jun 1998 19:58:18 -0700
- In-reply-to: <9806111526.AA19795@xxxxxxxxxxxxxxxxx>
- References: <9806111526.AA19795@xxxxxxxxxxxxxxxxx>
On Jun 11, 5:26pm, Peter Stephenson wrote:
} Subject: Re: Bugreport zsh 3.1.2: Shell exits prematurely after aborting h
}
} I had a look at this again, and I believe my previous analysis, that
} the lastc variable wasn't getting set properly, was the correct
} one. This time I followed the problem at bit further back.
} In my case, /etc/zshenv was being sourced immediately before the
} command loop started. At EOF, inputline() returned false; this caused
} ingetc() to set lastc to ' ', the behaviour which I found suspect.
This patch certainly does seem to stop the shell from exiting. I still
think there's an EOF being incorrectly propagated when the bck-i-search:
prompt is interrupted with C-c, but perhaps that doesn't matter if this
masks it. Thanks for checking again, Peter.
Side note: What's the point of leaving out the 'a' in "bck"? Just to
make it the same number of characters as "fwd"?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author