From: david rayner <email@example.com> To: firstname.lastname@example.org Subject: Re: cd /u/N/v/ tab expansion Date: Fri, 8 Apr 2022 11:22:37 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAH+w=7b6u-pSNXSDG3-M49U62WTUuU7XAL9B2Zp8Jj+va8bPrg@mail.gmail.com> On 08/04/2022 00:11, Bart Schaefer wrote: > On Thu, Apr 7, 2022 at 1:20 PM zzapper <firstname.lastname@example.org> wrote: >>> % ls /usr/l/b >>> >>> If I hit TAB again: >>> >>> % ls /usr/l/b >>> libexec/ local/ >> One issue I had was that it was only offering me two of the possible 6 >> sub-directories > If you look at my example, I was only offered libexec and local even > though there is a /usr/lib directory. But there's no file matching > "b*" in /usr/lib, so "lib" is excluded. > Wow in the end my problem was all PEBCAK zsh can only complete if there is one or more existing set of subdirectories e.g. cd /z/z/z will not expand as no such hierarchy exists on my pc but as you get no warning message you may (incorrectly) think the feature isn't working whereas cd /e/X/f/<tab> successfully expands to cd /etc/X11/fonts/
next prev parent reply other threads:[~2022-04-08 10:23 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 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 [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: cd /u/N/v/ tab expansion' \ /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
Code repositories for project(s) associated with this 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).