From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Gabor Maghera <gmaghera@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Completing arguments containing the colon character
Date: Sat, 29 Oct 2011 01:25:14 +0200 [thread overview]
Message-ID: <20111028232514.GA31749@daniel3.local> (raw)
In-Reply-To: <CAOzw3LawhuE4JVV7EJrkcoaqbwiJjwGGprM2s=-Sg0qka6=npg@mail.gmail.com>
Gabor Maghera wrote on Fri, Oct 28, 2011 at 16:12:05 -0700:
> We use a naming standard for Perforce specs of the form
> "<username>::<arbitrary>". Zsh autocompletion cannot process these entries,
> due to the colon character being used as a list separator by its mechanism
> (as I understand).
>
> Is there a way to make it work? I've been perusing the man page for
> zcompsys, as well as the _perforce completion module, but I'm not sure it's
> possible.
>
> Here is an example of what the erroneous completions look like:
> % p4 client -o p4droid<tab><tab>
> p4droid --
> :PerforceTriggers:2009/12/29 root /opt/local/perforce/trigger_scripts
> 'Created by p4droid. '
> p4droid -- :triggers:2009/12/18
> root /Workspace/trigger_test 'Created by gabor.maghera. '
>
> The full entry names are p4droid::PerforceTriggers and p4doird::triggers.
>
So I assumed you'd like
% p4 client -o p4droid<tab>
to suggest 'p4droid::PerforceTriggers' and 'p4doird::triggers'?
I don't know how to do that, but it's definitely possible:
% perldoc File::<tab>
File::Basename File::DosGlob File::Listing File::Spec::Functions File::Spec::Win32
File::CheckTree File::Fetch File::Path File::Spec::Mac File::stat
File::Compare File::Find File::Spec File::Spec::OS2 File::Temp
File::Copy File::Glob File::Spec::Cygwin File::Spec::Unix
File::Copy::Recursive File::GlobMapper File::Spec::Epoc File::Spec::VMS
> Thanks in advance,
> Gabor
HTH,
Daniel
next prev parent reply other threads:[~2011-10-28 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 23:12 Gabor Maghera
2011-10-28 23:25 ` Daniel Shahaf [this message]
2011-10-29 18:30 ` Peter Stephenson
2011-10-31 19:34 ` Gabor Maghera
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=20111028232514.GA31749@daniel3.local \
--to=d.s@daniel.shahaf.name \
--cc=gmaghera@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).