From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: Question
Date: Tue, 11 Apr 2000 10:36:00 +0200 (MET DST) [thread overview]
Message-ID: <200004110836.KAA03936@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 11 Apr 2000 12:22:47 +0400
Andrej Borsenkow wrote:
> > A matter of replacing `shout' in several places with the pipe. But
> > then there is the issue of starting the external command... And what
> > to do with menu-selection? And the terminal codes used by complist?
>
> Yes, exactly for this reason I'd really prefer built-in solution if at
> all possible. Keybinding is not an issue here (not really). But, of
> course, not in this release.
>
> > Oh my, and I only asked if it would be better to mention the
> > number of
> > lines needed for the list when asking if it should be displayed... ;-)
> >
> > And noone has answered that yet (unless Andrej meant that it would be
> > better).
>
> I have not answered because I do not actually care. What matters to me
> is the ability to see the full list. If I'm on X11 I can scroll - and if
> I'm on tty, it does not help anyway. May be, something like "output
> does not fit on screen" would be nice - currently, it is not obvious.
> That is, there are two cases
>
> - list can be shown in full, but user set it to small value
> - ilst does not fit at all
>
> To distinguish between them is nice.
This is done by the value of $LISTMAX:
- zero: ask if list is bigger than screen
- positive: ask if more matches than that
- negative: ask if more lines than that
Hm, maybe if we turn it into a scalar and make a value of `scroll' (or
`page') allow a very simple pager, builtin (which I, too, definitely
prefer), that is used if the list doesn't fit on the screen, with a
few keys:
- space: next screen (surprise!)
- return: next line
- q: stop listing
- <any>: stop listing and process key as usual
Going back in the list is a problem...
> The problem is, with all power of Zsh completion, I'm getting in habit
> to simply press TAB and see list of command options :-) And it is
> exactly this case, when output mostly does not fit on a screen.
I like to hear that. The first sentence, that is ;-)
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev reply other threads:[~2000-04-11 8:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 8:13 Question Sven Wischnowsky
2000-04-11 8:22 ` Question Andrej Borsenkow
2000-04-11 8:36 ` Sven Wischnowsky [this message]
2000-04-11 9:51 ` Question Sven Wischnowsky
2000-04-11 10:03 ` Question Andrej Borsenkow
2000-04-11 15:45 ` Question Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-04-12 8:51 Question Sven Wischnowsky
2000-04-12 8:56 ` Question Andrej Borsenkow
2000-04-12 16:06 ` Question Bart Schaefer
2000-04-10 8:24 Question Sven Wischnowsky
2000-04-10 16:49 ` Question Oliver Kiddle
2000-04-10 8:05 Question Sven Wischnowsky
2000-04-10 8:09 ` Question Andrej Borsenkow
2000-04-11 20:19 ` Question Peter Stephenson
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=200004110836.KAA03936@beta.informatik.hu-berlin.de \
--to=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).