From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: _match and auto menu with multipath again
Date: Thu, 17 Jun 1999 13:27:37 +0400 [thread overview]
Message-ID: <002101beb8a3$a36b97b0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199906170837.KAA04058@beta.informatik.hu-berlin.de>
>
> I wasn't completely sure what behavior you want in which case, so I
> just added two new configuration keys:
>
> path_cursor
> if this is set to a non-empty string, the cursor will be placed
> after the ambiguous pathname component even if menucompletion is
> used
>
> match_insert
> if this is set to anything starting with `unambig', menucompletion
> is only started (by the _match completer, obviously) if no
> unambiguous string that is at least as long as the original string
> could be generated
>
> Does any of these do what you want? Note that setting `match_insert=unambig'
> may sometimes remove a short pattern if enough components further up
> the path were expanded. This is a bit ugly, yes, but I can't think of
> an easy way to find out where that precious pattern is which one might
> want to have preserved.
>
Wow! I personally love the latter:
bor@itsrm2:~%> compconf match_insert=unambig
bor@itsrm2:~%> l /a/p/u/z/z*22*<TAB>
bor@itsrm2:~%> l /archive/pub/unix/z/z*22*
zip/ zsh/ ^ cursor here
and now I can complete ambiguous path component and hit TAB again.
Now, does it look sensible to others? If it is more natural, may be, we should
make it default?
/andrej
Thank you, Sven!
next prev parent reply other threads:[~1999-06-17 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-17 8:37 Sven Wischnowsky
1999-06-17 9:27 ` Andrej Borsenkow [this message]
1999-06-21 7:53 ` pws-23: " Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
1999-06-15 13:05 Andrej Borsenkow
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='002101beb8a3$a36b97b0$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=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).