From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: cvs completion does not support partial path completion
Date: Fri, 4 May 2001 16:26:14 +0000 [thread overview]
Message-ID: <1010504162614.ZM19293@candle.brasslantern.com> (raw)
In-Reply-To: <1010504051600.ZM18512@candle.brasslantern.com>
On May 4, 5:16am, Bart Schaefer wrote:
} Subject: PATCH: Re: cvs completion does not support partial path completio
}
} The rest of the hunks remove explanation strings from calls to
} _arguments or _alternative in cases where the called action-function
} will eventually supply a more accurate one. This prevents messages
} that say e.g. "No matches for `file' or `removed file'" when in fact
} only `removed file' was really attempted. Are there other side-effects
} of this that I've missed?
Yes, there were. `*::_cvs_files' is interpreted as `*::_cvs_files: '
which of course will never do. Is there _any_ way to specify an empty
message with the `*:...' form of _arguments spec?
--
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
next prev parent reply other threads:[~2001-05-04 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 14:05 Andrej Borsenkow
2001-04-27 12:20 ` Sven Wischnowsky
2001-04-27 13:08 ` Andrej Borsenkow
2001-04-27 13:22 ` Sven Wischnowsky
2001-04-27 17:54 ` Bart Schaefer
2001-04-30 8:17 ` Sven Wischnowsky
2001-04-30 16:56 ` Bart Schaefer
2001-05-01 9:39 ` Tanaka Akira
2001-05-04 5:16 ` PATCH: " Bart Schaefer
2001-05-04 16:26 ` Bart Schaefer [this message]
2001-05-07 7:58 ` Sven Wischnowsky
2001-05-07 14:52 ` Bart Schaefer
2001-05-08 8:45 ` Sven Wischnowsky
2001-05-04 16:39 ` 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=1010504162614.ZM19293@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.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).