From: Scott Frazer <frazer.scott@gmail.com>
To: zsh-users@zsh.org
Cc: zsh-users@zsh.org
Subject: Re: Dynamic named directories and completion
Date: Fri, 23 Feb 2018 09:41:47 -0500 [thread overview]
Message-ID: <113952bc-b4e7-511d-7b3c-7cf2144c2174@gmail.com> (raw)
In-Reply-To: <m3po4wnni0.fsf@luffy.cx>
On 2/23/18 3:01 AM, Vincent Bernat wrote:
> ❦ 22 février 2018 17:54 -0500, Scott Frazer <frazer.scott@gmail.com> :
>
>> zsh_directory_name ()
>> {
>> emulate -L zsh
>> setopt extendedglob
>> local -a seg;
>> seg=(${(s:/:)PWD%/*})
>> if [[ $1 = n ]]; then
>> typeset -ga reply
>> reply=( /${(j:/:)seg[1,(I)$2]} )
>> elif [[ $1 = c ]]; then
>> local expl
>> _wanted values expl 'parent dirs' compadd -S\] -a seg
>> else
>> return 1
>> fi
>> return 0
>> }
>>
>> Suppose I am in directory /aaa/bbb/ccc/ddd/eee and want to go up to directory
>> ccc and then down into another directory. If I do:
>>
>> cd ~[c<TAB>
>>
>> it correctly completes to:
>>
>> cd ~[ccc]
>>
>> If I hit enter at this point I go to /aaa/bbb/ccc. So far so good. If I
>> try to start completion, like so:
>>
>> cd ~[ccc]/<TAB>
>>
>> zsh doesn't give me options for directories under ccc, it thinks '/' is
>> the command I'm trying to complete. Is there a way to make this work?
>
> I don't see anything wrong in your code and for me, it works as you
> expect (zsh 5.4.2). Does "echo ~[ccc]" returns the right value?
>
Yes, "echo ~[ccc]" works correctly. I'm using zsh 5.3 so maybe there is some
difference there. Perhaps there is some difference in options/modules/etc. If
I cut my .zshrc down to a minimum:
autoload -Uz compinit
compinit
zstyle ':completion:*' verbose yes
zstyle ':completion:*' menu select=2
zstyle ':completion:*:messages' format '%d'
zstyle ':completion:*' group-name ''
zstyle ':completion:*' squeeze-slashes true
zstyle ':completion:*:descriptions' format "%UCompleting %d:%u"
zstyle ':completion:*:warnings' format "No matches for: %d"
(with the above zsh_directory_name() too of course), plain ~[whatever] works
but ~[whatever]/ will not complete paths. Do you have anything non-standard
in your completion?
Scott
next prev parent reply other threads:[~2018-02-23 14:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 22:54 Scott Frazer
2018-02-23 0:29 ` [RFC PATCH] _path_files: teach zsh_directory_name Takeshi Banse
2018-02-23 1:19 ` _path_files: fix copy paste error Takeshi Banse
2018-02-23 1:30 ` _path_files: fix copy paste error (2/2) Takeshi Banse
2018-02-23 8:01 ` Dynamic named directories and completion Vincent Bernat
2018-02-23 14:41 ` Scott Frazer [this message]
2018-02-23 15:02 ` Takeshi Banse
2018-02-23 14:42 ` Scott Frazer
2018-02-24 19:34 ` Peter Stephenson
2018-02-24 19:49 ` Mikael Magnusson
2018-02-24 20:12 ` Peter Stephenson
2018-02-26 14:31 ` Scott Frazer
2018-02-26 13:53 ` Scott Frazer
2018-02-26 14:47 ` Peter Stephenson
2018-02-26 16:44 ` Scott Frazer
2018-02-26 20:08 ` Peter Stephenson
2018-02-26 21:22 ` Peter Stephenson
2018-02-26 17:49 ` Mikael Magnusson
2018-02-26 17:55 ` Peter Stephenson
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=113952bc-b4e7-511d-7b3c-7cf2144c2174@gmail.com \
--to=frazer.scott@gmail.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).