zsh-workers
 help / color / mirror / code / Atom feed
From: Danek Duvall <duvall@comfychair.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: _multi_parts and -q
Date: Mon, 20 Jun 2011 22:40:43 -0700	[thread overview]
Message-ID: <20110621054043.GA9528@lorien.comfychair.org> (raw)
In-Reply-To: <110620220334.ZM8712@torch.brasslantern.com>

On Mon, Jun 20, 2011 at 10:03:34PM -0700, Bart Schaefer wrote:

> --- Completion/Base/Utility/_multi_parts	21 Dec 2010 16:41:14 -0000
> +++ Completion/Base/Utility/_multi_parts	21 Jun 2011 05:00:16 -0000
> @@ -116,7 +116,8 @@
>  	  compadd "$group[@]" "$expl[@]" "$sopts[@]" \
>                    -M "r:|${sep}=* r:|=* $matcher" - $pref$matches
>          else
> -	  if (( $matches[(I)${tmp1[1]}${sep}*] )); then
> +	  if (( $matches[(I)${tmp1[1]}${sep}*] )) &&
> +            ! (( $matches[(I)${tmp1[1]}] )); then
>  	    compadd "$group[@]" "$expl[@]" -p "$pref" -r "$sep" -S "$sep"
> "$opts[@]" \
>                      -M "r:|${sep}=* r:|=* $matcher" - "$tmp1[1]"
>            else

This doesn't seem to do the trick for me.  The slash is auto-removed, all
right, but immediately after I hit tab.  I can backspace over that space,
put in a slash (hitting tab will do that for me), and start completing
again, but then it's weird -- the next level in the hierarchy is presented
twice -- once with a slash and once without.

Danek

> By the way, do NOT pass an empty separator to _multi_parts.  Infinite loop.

_multi_parts should be able to check for that, no?

Danek


  reply	other threads:[~2011-06-21  5:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 21:50 Danek Duvall
2011-06-18 19:44 ` Bart Schaefer
2011-06-18 19:52 ` Peter Stephenson
2011-06-18 20:03   ` Bart Schaefer
2011-06-18 21:07     ` Peter Stephenson
2011-06-20 15:44       ` Danek Duvall
2011-06-21  5:03       ` Bart Schaefer
2011-06-21  5:40         ` Danek Duvall [this message]
2011-06-21  8:02           ` 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=20110621054043.GA9528@lorien.comfychair.org \
    --to=duvall@comfychair.org \
    --cc=schaefer@brasslantern.com \
    --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).