Re: up-line-or-search question

[Bart Schaefer <schaefer@brasslantern.com>]

On Wed, 27 Mar 2002, Oliver Kiddle wrote:

> On Wed, Mar 27, 2002 at 04:30:03PM +0000, Bart Schaefer wrote:
> >
> > Not exactly -- __searching will get cleared as soon as a search fails and
> > a simple up/down motion is done -- but you're right, the test should be
> > [[ $__searching = *-line-or-search && $LASTWIDGET = *-line-or-search ]]
> > or something along those lines.
>
> I'm not quite sure what that is trying to achieve.

It's just treating searches in both directions as equivalent for purposes
of whether to re-use the saved cursor position (or string) or to start a
new search with the current $LBUFFER.

> I also can't remember how I got it not to work in the first place
> because it is now.

Search up successfully, and then immediately try to search down again?

> Okay, I'll probably put the push-line-or-edit in when enabled with
> a style too then. Could we maybe agree a common prefix for the
> contexts of the styles in Functions/Zle - ':zle:' maybe?

E.g., change :predict to :zle:predict ?

I wish we'd thought about that sooner ... it's not a bad idea, but it
means changing predict-on, incremental-complete-word, etc. ... maybe
we can use the excuse of differentiating complex stateful widgets from
simple zle functions.