From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH and Re: simulation of dabbrev-expand
Date: Mon, 11 Oct 1999 22:44:08 +0100 [thread overview]
Message-ID: <19991011224408.B23117@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <199910111112.NAA02526@beta.informatik.hu-berlin.de>
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
>
> [ Trying to reduce the number of replies by answering multiple
> messages... ]
Welcome back to the fun :-)
> First, the `design decision' comes from a time when one couldn't
> execute shell code (and look at the current state) during
> completion. Then, I think it is still right to execute the probably
> expansive sorting and uniquifying as seldom as possible -- and in most
> cases this is really only needed at the end. But I after thinking some
> more about this, I really think, the solution to do the calculation
> when one of the `nmatches' keys is used is ok.
Yep, this should be fine I guess.
> ...by adding a key, say `list_lines' or whatever which would allow us
> to write shell code that can find out if the listing code would ask
> (well, of course we could also check this in C and have a key saying
> whether it would ask, but that check is easy and knowing the number of
> lines may be intersting anyway, maybe, hm...). Anyway, with the
> relatively new `calclist()' this would be quite easy to implement
> (heck, we could give many different types of information about the
> list).
That would be nice too. Then you could be quite intelligent about
what to display. For example you might want to specify LIST_MAX as
multiples of the screen length.
> > Selecting completion groups would be a nice feature in any case.
>
> This is something I want to achieve (see 12241, at least if I
> understand you correctly) with the grouping anhancements to the
> completion system discussed lately (keywords: tags, priorities, and
> Peter's auto-documentation suggestion).
I look forward to it :-)
next prev parent reply other threads:[~1999-10-11 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-11 11:12 Sven Wischnowsky
1999-10-11 21:44 ` Adam Spiers [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-23 14:23 Sven Wischnowsky
1999-09-25 14:45 ` Adam Spiers
1999-09-23 8:38 Sven Wischnowsky
1999-09-23 13:44 ` Adam Spiers
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=19991011224408.B23117@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--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).