zsh-users
 help / color / mirror / code / Atom feed
From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@zsh.org
Subject: Re: Slow completion
Date: Thu, 7 Mar 2013 21:33:35 +0100	[thread overview]
Message-ID: <khatiu$kgc$1@ger.gmane.org> (raw)
In-Reply-To: <130307080445.ZM12249@torch.brasslantern.com>

* Bart Schaefer (Thu, 07 Mar 2013 08:04:45 -0800)
> I'm not a regular cygwin user (in fact it's probably been 15 years 
since
> I even touched a box with cygwin, now that I think about it) so you'll
> have to (a) forgive any inaccuracies and (b) remind me how it is that
> "cadaver" gets into the "relative" completion list in the first place,
> since it is not a file on disk.

Not really sure about the "exe magic". I think Cygwin just adds it. 
Windows requires the .exe extension for the file itself but not for the 
invocation 
(PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC)

> However, I think it's wrong to assert this is "inconsistent" completion.
> You're not completing the same thing.  I'm pretty sure "cada" is being
> completed for the "path-commands" group, while /usr/bin/cada is in the
> "executables" (executable file or directory) group.

Okay, I got it.

> It might be possible to get the effect of completion_strip_exe with a
> matcher style, something like (though I don't think this works)
> 
>     zstyle ':completion:*:-command-:*' matcher \
>         'R:|.[eE][xX][eE]=.[eE][xX][eE]'

Doesn't work but thanks for trying.

Thorsten


  reply	other threads:[~2013-03-07 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 21:40 Thorsten Kampe
2013-03-07 10:22 ` Peter Stephenson
2013-03-07 11:44   ` Mikael Magnusson
2013-03-07 12:08     ` Peter Stephenson
2013-03-07 16:04 ` Bart Schaefer
2013-03-07 20:33   ` Thorsten Kampe [this message]
2013-03-07 23:38   ` Oliver Kiddle
2013-03-08 15:45     ` joe M
2013-03-11 16:21       ` 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='khatiu$kgc$1@ger.gmane.org' \
    --to=thorsten@thorstenkampe.de \
    --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).