From: zzapper <zsh@rayninfo.co.uk>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: cd /u/N/v/ tab expansion
Date: Thu, 7 Apr 2022 21:20:03 +0100 [thread overview]
Message-ID: <2b388cce-1412-36cd-9a90-d58f853ee830@rayninfo.co.uk> (raw)
In-Reply-To: <CAH+w=7ZtQVCJDCe0OAXPKRUa8zU1kgDMDu-y82BvHmOk+reYRw@mail.gmail.com>
> What's odd about it? The behavior should be that the unambiguous part
> at the left is completed, and then the cursor stops at the first
> ambiguous point. For example, if I do:
>
> % ls /u/l/b<TAB>
>
> I get, with cursor after the "l" (over the third "/"):
>
> % ls /usr/l/b
>
> If I hit TAB again:
>
> % ls /usr/l/b
> libexec/ local/
>
> When does this fail for you?
>
>> Q1) where is the doc for this?
> Under the entry for _path_files.
>
>> Has something in my setup overloaded this?
> No way for us to tell. Have you tried using the ctrl+x question-mark
> binding to get a completion traceback?
Thanks Bart, I will try and be more precise my 'oddly' and report back
to this thread.
One issue I had was that it was only offering me two of the possible 6
sub-directories
> zzapper
next prev parent reply other threads:[~2022-04-07 20:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:40 zzapper
2022-04-07 20:11 ` Bart Schaefer
2022-04-07 20:20 ` zzapper [this message]
2022-04-07 23:11 ` Bart Schaefer
2022-04-08 9:53 ` zzapper
2022-04-08 17:57 ` Bart Schaefer
2022-04-08 10:22 ` david rayner
2022-04-08 18:09 ` Bart Schaefer
2022-04-10 1:04 ` Tomasz Pala
2022-04-10 14:32 ` Tomasz Pala
2022-04-10 16:27 ` Tomasz Pala
2022-04-10 16:32 ` Tomasz Pala
2022-04-10 17:45 ` Tomasz Pala
2022-04-10 18:05 ` Tomasz Pala
2022-04-16 14:17 ` Tomasz Pala
2022-04-17 3:00 ` Bart Schaefer
2022-04-17 16:17 ` Tomasz Pala
2022-04-17 18:15 ` Bart Schaefer
2022-04-17 18:44 ` Bart Schaefer
2022-04-17 18:32 ` Bart Schaefer
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=2b388cce-1412-36cd-9a90-d58f853ee830@rayninfo.co.uk \
--to=zsh@rayninfo.co.uk \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/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).