Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: A couple completion glitches
- X-seq: zsh-workers 12060
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>, Zsh Workers <zsh-workers@xxxxxxxxxxxxxx>
- Subject: Re: A couple completion glitches
- Date: Sun, 25 Jun 2000 02:21:52 +0000
- In-reply-to: <1000624230022.ZM16742@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <Pine.LNX.4.21.0006241215430.3626-100000@xxxxxxxxxxxxxxx> <1000624230022.ZM16742@xxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author