zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: side effect of "select=long"
Date: Mon, 22 May 2000 15:44:03 +0400	[thread overview]
Message-ID: <000601bfc3e3$06f78320$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200005221129.NAA19513@beta.informatik.hu-berlin.de>

>
> 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


  reply	other threads:[~2000-05-22 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-22 11:29 Sven Wischnowsky
2000-05-22 11:44 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-22 10:54 Andrej Borsenkow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601bfc3e3$06f78320$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).