From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completion after //
Date: Wed, 19 Jan 2000 17:42:39 +0100 (MET) [thread overview]
Message-ID: <200001191642.RAA19840@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Alexandre Duret-Lutz's message of 19 Jan 2000 12:17:37 +0100
Alexandre Duret-Lutz wrote:
> >>> "Tanaka" == Tanaka Akira <akr@jaist.ac.jp> 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 ?
I fear it will mess up completion inside braces (only if both multiple
slashes and braces are used at the same time), but: try it. Using a
style for it, of course ;-)
When I wrote _path_files I was tempted to disallow in-path completion
inside `//' at least when that appears at the beginning, because, if
I'm not completely mistaken, there is or once was a Unix version where
this had special meaning.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-01-19 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-19 16:42 Sven Wischnowsky [this message]
2000-01-20 9:12 ` Alexandre Duret-Lutz
-- strict thread matches above, loose matches on Subject: below --
2000-01-21 13:55 Sven Wischnowsky
2000-01-20 9:23 Sven Wischnowsky
2000-01-20 10:21 ` Alexandre Duret-Lutz
2000-01-19 9:51 completion after ../ Tanaka Akira
2000-01-19 11:17 ` completion after // Alexandre Duret-Lutz
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=200001191642.RAA19840@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).