zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: scrolling completion lists (was: Re: Questions)
Date: Mon, 17 Apr 2000 12:47:09 +0100	[thread overview]
Message-ID: <0FT5004N3SQK6P@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Mon, 17 Apr 2000 13:10:41 +0200." <200004171110.NAA15088@beta.informatik.hu-berlin.de>

> I had been thinking about doing this, but the patch below uses a
> simple statusline below the menu when it is too big to fit on the
> screen and the $SELECTSTATUS parameter is set. That may contain some
> %-escaped (%l - line information, %m - match information, %p -
> Top/Bottom/%).

This is fine, but it should probably have some default value, which could
be set in the shell functions if that's possible, e.g.
  SELECTSTATUS='Scrolling active: current selection at %p'
although I've put a %B at the front.

At the moment it doesn't alter the default LISTMAX.  That's tricky, since
LISTMAX is set in params.c.  But it would be preferable to have that
reflect the fact that scrolling is going to be used instead of limiting the
display.  More precisely, it would be preferable for LISTMAX not to be set
if it's going to be used, and to be used if it's explicitly set, I suppose.
One problem is that until zsh/complist is loaded, LISTMAX *will* be used.
Maybe that means we just document the fact it will be ignored when using
complist.

-- 
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2000-04-17 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-17 11:10 Sven Wischnowsky
2000-04-17 11:47 ` Peter Stephenson [this message]
2000-04-17 12:11 Sven Wischnowsky
2000-04-17 13:01 ` Peter Stephenson
2000-04-18  7:34 Sven Wischnowsky
2000-04-18  8:47 ` Peter Stephenson
2000-04-18  9:16 ` Peter Stephenson
2000-04-18  9:32 Sven Wischnowsky
2000-04-18  9:47 ` Peter Stephenson
2000-04-19  6:47 Sven Wischnowsky

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=0FT5004N3SQK6P@la-la.cambridgesiliconradio.com \
    --to=pws@cambridgesiliconradio.com \
    --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).