Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!nucsrl!gore!jacob
From: jacob@gore.com (Jacob Gore)
Newsgroups: gnu.bash.bug
Subject: Re: reverse i-search
Message-ID: <30002@gore.com>
Date: 4 Jul 89 18:12:24 GMT
References: <89Jul2.215402edt.10369@neat.ai.toronto.edu>
Reply-To: jacob@gore.com (Jacob Gore)
Organization: Gore Enterprises
Lines: 22

/ gnu.bash.bug / lamy@ai.utoronto.ca (Jean-Francois Lamy) / Jul  3, 1989 /
   ...When a reverse i-search in emacs shows
   "foo" in the prompt, and you type "bar", you expect it to search for
   "foobar", not "bar".  So one of two things: either make bash search for
   "foo" when you type ^R after typing "foo" (which resembles) tcsh, or
    clear the prompt.  In any case, make the prompt match what is being
    searched for.
----------

But it's not the prompt that's not being cleared, it's the text.  Emacs
shows you the text being found in a window, and the string being searched
for in the minibuffer.  Bash does not show a minibuffer, all you see is the
text being found.  When you start a reverse i-search, the text cursor stays
at the same position, both in emacs and in bash.

I don't think the last text line should be cleared when you enter reverse
i-search.  I like being able to use reverse i-search to move around in the
current line, especially if it's a long one.  You seem to assume that it is
always used to find a DIFFERENT line.

--
Jacob Gore	Jacob@Gore.Com		{nucsrl,boulder}!gore!jacob