From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Preventing sorting in completers
Date: Mon, 14 Jul 2003 17:11:39 +0000 [thread overview]
Message-ID: <1030714171139.ZM6396@candle.brasslantern.com> (raw)
In-Reply-To: <15028.1058200902@csr.com>
On Jul 14, 5:41pm, Peter Stephenson wrote:
} Subject: Re: Preventing sorting in completers
}
} For example, the following very lightly tested function where I've tried
} not to screw up _expand but fell into apathy at the thought of actually
} testing whether I had.
I think what you've done will change the behavior of _expand in those
cases where the internal sort done by the completion system does not
agree with the sort performed by ${(o)exp}. Depending on the context
used to set the style, of course.
I'm not sure what the other ramifications of the zstyle context may be;
_expand uses
zstyle -s ":completion:${curcontext}:" sort sort
whereas with the patch _description uses
zstyle -s ":completion:${curcontext}:$1" sort sort
} I think this makes the direct use in _history redundant.
Not quite, because _history also uses the shorter context name:
if zstyle -t ":completion:${curcontext}:" sort; then
Is there an obvious way to resolve that, without breaking working styles?
next prev parent reply other threads:[~2003-07-14 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wuenkuod.fsf@ceramic.fifi.org>
2003-07-13 18:17 ` Bart Schaefer
2003-07-14 15:11 ` Peter Stephenson
2003-07-14 16:11 ` Danek Duvall
2003-07-14 16:31 ` Bart Schaefer
2003-07-14 16:41 ` Peter Stephenson
2003-07-14 17:11 ` Bart Schaefer [this message]
2003-07-14 17:31 ` Peter Stephenson
2003-07-14 19:14 ` Bart Schaefer
2003-07-15 9:42 ` Peter Stephenson
2003-07-15 16:16 ` Bart Schaefer
2003-07-15 18:35 ` Peter Stephenson
2003-07-22 19:51 ` Philippe Troin
2003-07-23 9:23 ` Peter Stephenson
2003-07-23 19:12 ` Philippe Troin
2003-07-24 9:28 ` CVS (Re: Preventing sorting in completers) Oliver Kiddle
2003-07-14 20:13 ` Preventing sorting in completers Philippe Troin
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=1030714171139.ZM6396@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).