side effect of "select=long"

side effect of "select=long"

[Andrej Borsenkow]

If you set select=long, menu selection is started *only* if list does
not fit on screen - else menu completion is started. I bever intended
that - rather, my intention was to start menu selction *instead* of
displaying completion list. I always had 'select=0' to start menu
selection unconditionally - now I have no way to start it at all.

In other words, either select style should support something like
"select='0 long'" or this settings belong to other tag alltogether

-andrej

Have a nice DOS!
B >>

Re: side effect of "select=long"

[Sven Wischnowsky]

Andrej Borsenkow wrote:

> If you set select=long, menu selection is started *only* if list does
> not fit on screen - else menu completion is started. I bever intended
> that - rather, my intention was to start menu selction *instead* of
> displaying completion list. I always had 'select=0' to start menu
> selection unconditionally - now I have no way to start it at all.
> 
> In other words, either select style should support something like
> "select='0 long'" or this settings belong to other tag alltogether

Nonsense. What should that mean? `Start selection when the matches
don't fit on the screen, oh, *and* start selection always'??

You were asking for a way to start selection in listing-widgets when
the list doesn't fit on the screen. That's what `select=long-list' is
for, as explained in the docs.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de

RE: side effect of "select=long"

[Andrej Borsenkow]

>
> Nonsense. What should that mean? `Start selection when the matches
> don't fit on the screen, oh, *and* start selection always'??
>

Not at all. We have separately completion lists AND menu
completion/selection. First list is displayed (of course, with
corresponding settings) and then, on the second TAB, menu
completion/selection is started. So, that means `start selection INSTEAD
of list if matches do not fit on the screen and start selection ON THE
SECOND TAB always (assuming, it was not started already)'. What is so
nonsensical here? I just thought, it is simpler than (re-)implementing
full screen pager for lists - given, that we already have one for menu
selection.

> You were asking for a way to start selection in listing-widgets when
> the list doesn't fit on the screen. That's what `select=long-list' is
> for, as explained in the docs.
>

I was asking for a way to sart selection INSTEAD of list. I never asked
to change the way menu selection is selected (sorry for pun) instead of
menu completion. I beg pardon if I have not expressed myself clear
enough.

-andrej