help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: thomas@coldfix.de
Cc: zsh-workers@zsh.org
Subject: Re: Path with spaces in _canonical_paths
Date: Sun, 20 Nov 2022 19:57:23 -0800	[thread overview]
Message-ID: <CAH+w=7ZBYX3-X2AD_iDR6T4Yz8OdA1TE+YeC2qZmHdk+W=VbgA@mail.gmail.com> (raw)
In-Reply-To: <sympa.1668791373.628329.85325.773@zsh.org>

On Fri, Nov 18, 2022 at 9:42 AM <thomas@coldfix.de> wrote:
> I'm trying to use `_canonical_paths` (on zsh 5.9) to let the user autocomplete
> a fixed list of files. I hope I'm not using it incorrectly.

Tangentially to -workers:  Is _canonical_paths documented in the wrong
manual section?  It's lumped in with functions that are expected to
appear in the "completer" zstyle, which clearly it is not.

> compdef '_canonical_paths -N files files /tmp/My\ File' cmd
> cmd <Tab>
> Shows the following completions:
> /tmp/My File    (appears twice)
> /tmp/My\ File
> i.e. I get in total 3 entries for the same path

I'm not able to reproduce this using nothing but compinit plus the
compdef above.  I get just one completion, "/tmp/My\ File", regardless
of whether that file exists or not.

Try this:

debug_canonical_paths () {
  _canonical_paths -N files files /tmp/My\ File
compdef '_complete_debug debug_canonical_paths' cmd

Pressing TAB then drops a file in /tmp with a debug trace of the
execution of _canonical_paths.  In particular look at which "zstyle"
lookups are being done and which of those might be causing the extra
entries.  You can also look at the context around elements being added
to the "matches" array.

  reply	other threads:[~2022-11-21  3:58 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7ZBYX3-X2AD_iDR6T4Yz8OdA1TE+YeC2qZmHdk+W=VbgA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=thomas@coldfix.de \
    --cc=zsh-workers@zsh.org \


* 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


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).