From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Once more: "Do you wish to see all xxx possibilities?"
Date: Thu, 4 Nov 1999 10:47:15 +0100 (MET) [thread overview]
Message-ID: <199911040947.KAA11871@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Wed, 3 Nov 1999 20:07:05 +0300
Andrej Borsenkow wrote:
> I still do not understand, when it is printed. Looking in Zle/compresult.c:
>
> /* Maybe we have to ask if the user wants to see the list. */
> if ((!minfo.cur || !minfo.asked) &&
> ((complistmax && listdat.nlist > complistmax) ||
> (!complistmax && listdat.nlines >= lines))) {
>
> It means, that it should ask if either complistmax is set (value of
> $compconfig[list_max]?) or number of lines exceeds $LINES. It seems, that Zsh
> sometimes gets incorrect count in listdat.nlines. Consider:
Many years ago, documentation was invented:
LISTMAX
In the line editor, the number of filenames to list without asking
first. If set to zero, the shell asks only if the top of the
listing would scroll off the screen.
Even though `filenames' is definitely the wrong word here, I think it
should be clear enough.
And that's what the test you quoted above does. `complistmax' is the
atoi() of the value of `$compconfig[list_max]'. So, we ask if either
that is non-zero and the number of matches is larger than that value
or if the value is zero and the number of lines needed for the list is
larger that the screen height.
In other words: if you only want the list if it fits on the screen,
set `LISTMAX=0'.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-11-04 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-04 9:47 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-03 17:07 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=199911040947.KAA11871@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).