Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
completion after //
- X-seq: zsh-workers 9364
- From: Alexandre Duret-Lutz <duret_g@xxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: completion after //
- Date: 19 Jan 2000 12:17:37 +0100
- In-reply-to: Tanaka Akira's message of "19 Jan 2000 18:51:44 +0900"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <rsq1z7ev173.fsf@xxxxxxxxxxxxxxxxx>
>>> "Tanaka" == Tanaka Akira <akr@xxxxxxxxxxx> writes:
Tanaka> Sometimes completion after ../ frustrates me.
[...]
Along with the same lines, something I don't like is
that the path `a///////b' is not understand as 'a/b' by _path_files
(when I cut and past path names that contains doubled
slashes, it's annoying to not be able to complete after these).
I wanted to add :
# Squeeze sequences of slashes
PREFIX="${PREFIX//(\\/)#//}"
SUFFIX="${SUFFIX//(\\/)#//}"
[[ $PREFIX = */ ]] && SUFFIX=${SUFFIX#/}
at the beginning of _path_files, but then realized that
people may want to use `//' to do partial path completion.
Should this be tunable ?
--
Alexandre Duret-Lutz
Messages sorted by:
Reverse Date,
Date,
Thread,
Author