From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Cc: "Thomas Gläßle" <thomas@coldfix.de>
Subject: Re: Path with spaces in _canonical_paths
Date: Thu, 24 Nov 2022 00:12:56 +0000 [thread overview]
Message-ID: <20221124001256.GR27622@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7bUUbPfSKVgk+7+1PPvQYQ2OPwDakuz2Ps=4agOYk=hsQ@mail.gmail.com>
Bart Schaefer wrote on Wed, Nov 23, 2022 at 15:12:40 -0800:
> On Wed, Nov 23, 2022 at 3:06 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Anyway, I see you've extended it to clarify. Thanks for this.
>
> Remains to be seen if it works ... I still can't figure out how to
> cause that code path ("else") to be followed when I try to reproduce
> Thomas's error.
In the zsh tree,
.
_f() { _canonical_paths tag desc $PWD/README }
compdef _f f
f <TAB>
.
is enough for me to get the else path to be taken. For the variant with
-N and quoting,
.
touch /tmp/My\ File
ln -s /tmp slashtmp
compdef '_canonical_paths -N files files /tmp/My\ File' cmd
cmd <TAB>
.
gives
.
1 >>> files
2 /tmp/My\ File slashtmp/My File
That's with current HEAD and my nearly-minimal test setup (sets
little besides 'format', 'group-name', $PS1, $PS4, and $fpath).
Cheers,
Daniel
next prev parent reply other threads:[~2022-11-24 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 17:41 thomas
2022-11-21 3:57 ` Bart Schaefer
2022-11-21 10:47 ` thomas
2022-11-21 16:30 ` Bart Schaefer
2022-11-21 17:41 ` Thomas Gläßle
2022-11-21 21:32 ` Bart Schaefer
2022-11-23 14:13 ` Daniel Shahaf
2022-11-23 21:36 ` Bart Schaefer
2022-11-23 22:24 ` Daniel Shahaf
2022-11-23 22:42 ` Bart Schaefer
2022-11-23 23:06 ` Daniel Shahaf
2022-11-23 23:12 ` Bart Schaefer
2022-11-24 0:12 ` Daniel Shahaf [this message]
2022-11-24 18:42 ` Bart Schaefer
2022-11-23 23:36 ` Thomas Gläßle
2022-11-23 23:40 ` Thomas Gläßle
2022-11-24 18:51 ` 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=20221124001256.GR27622@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=thomas@coldfix.de \
--cc=zsh-workers@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).