zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Redo _zle using _arguments
Date: Wed, 4 Oct 2000 15:05:43 +0000	[thread overview]
Message-ID: <1001004150543.ZM22391@candle.brasslantern.com> (raw)
In-Reply-To: <200010041247.OAA09608@beta.informatik.hu-berlin.de>

On Oct 4,  2:47pm, Sven Wischnowsky wrote:
} 
} Bart Schaefer wrote:
} 
} > I also suspect there may be a bug in comparguments -- the '(*)-x' form of
} > optspec is supposed to mean that the '*:msg:act' form is not completed
} > when -x is on the command line, but that doesn't seem to happen (or at
} > least, not always).
} 
} Hm, I had a look but couldn't find a bug. Could you give me an example?

Sure.  Completion after "zle -R -c":

zagzig[501] zle -R -c <TAB>
Completing status line
Completing strings to list

The call to _arguments was:

      _arguments -s \
        "-R[redisplay]" \
	"(*)-c[clear listing]" \
	"(-)::status line: " "*:strings to list: "

Since "(*)-c" is there, and -c is on the line, the "*:strings to list: "
clause should never be activated.  Yet there's the description string for
it, in the listing.  If I go on to add something for the status line:

zagzig[501] zle -R -c something <TAB>
Completing no more arguments

What I expected the first time was either just "Completing status line"
or that plus "no more arguments", but not "strings to list".

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-10-04 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-04 12:47 Sven Wischnowsky
2000-10-04 15:05 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-05  8:53 Sven Wischnowsky
2000-10-04 10:43 Sven Wischnowsky
2000-09-11  5:13 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=1001004150543.ZM22391@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).