From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Hong Xu <hong@topbug.net>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Feature request: readline's completion-prefix-display-length option
Date: Thu, 19 May 2016 21:14:28 +0000 [thread overview]
Message-ID: <20160519211428.GA14104@tarsus.local2> (raw)
In-Reply-To: <CAH+w=7aYcxp73F2koe1nVBRMR8jwJ5eYLAyMi2_35FEX9=dJXw@mail.gmail.com>
Bart Schaefer wrote on Sun, May 15, 2016 at 04:50:50 -0700:
> On Sat, May 14, 2016 at 11:08 PM, Hong Xu <hong@topbug.net> wrote:
> >
> > I believe that readline's completion-prefix-display-length is a great
> > option to have for zle. This option enables the common part of long
> > completions to be represented by ellipsis, so the options in the
> > completion list would not be too long in many cases.
>
> There might be a deviously clever way to do this with the list-colors
> style, similar to the way that show-ambiguity is implemented.
Deviously clever solutions aside, isn't this exactly what the -d option
to compadd is for? I imagine prior to calling compadd, the following
preprocessing could be invoked:
if -d not passed:
argument_to_-d = argument_to_-a
for each element of argument_to_-d:
if this element starts with ${PREFIX}
replace the first ${#PREFIX} characters of this element with an ellipsis
However, I'm not sure where this preprocessing should be invoked from.
CHeers,
Daniel
next prev parent reply other threads:[~2016-05-19 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 6:08 Hong Xu
2016-05-15 11:50 ` Bart Schaefer
2016-05-19 21:14 ` Daniel Shahaf
2016-06-02 13:28 ` Daniel Shahaf
2016-05-19 21:14 ` Daniel Shahaf [this message]
2016-06-02 5:42 ` Bart Schaefer
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=20160519211428.GA14104@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=hong@topbug.net \
--cc=zsh-workers@zsh.org \
/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).