From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Wayne Davison <wayned@users.sourceforge.net>,
Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Re: A couple completion glitches
Date: Sun, 25 Jun 2000 02:21:52 +0000 [thread overview]
Message-ID: <1000625022152.ZM16855@candle.brasslantern.com> (raw)
In-Reply-To: <1000624230022.ZM16742@candle.brasslantern.com>
On Jun 24, 11:00pm, I wrote:
}
} } In my mind, I would like it to always order the full expansion and the
} } original string into the same places, regardless of ASCII order (to
} } make it more consistent). Perhaps always put the multi-item expansion
} } first and the original string last?
}
} This could be accomplished by having _expand put the original string in
} its own compadd group. That means a bit of restructuring of _expand to
} store the original string separately until it is known whether there are
} any other expansions possible.
On further investigation, I find I'm wrong about this, too; I misread the
last part of _expand where the compadd commands are performed.
The original completion already IS being added in a separate completion
group; the only thing you need to do to have it always listed last is
zstyle ':completion:*' group-name ''
If you don't like that behavior for regular completion, limit it:
zstyle ':completion:*:expand:*' group-name ''
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-06-25 2:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-24 19:54 Wayne Davison
2000-06-24 23:00 ` Bart Schaefer
2000-06-24 23:21 ` Bart Schaefer
2000-06-25 8:38 ` Wayne Davison
2000-06-25 17:01 ` Bart Schaefer
2000-06-25 2:21 ` Bart Schaefer [this message]
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=1000625022152.ZM16855@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wayned@users.sourceforge.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).