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: Mon, 7 May 2001 14:52:18 +0000 [thread overview]
Message-ID: <1010507145218.ZM27680@candle.brasslantern.com> (raw)
In-Reply-To: <200105070758.JAA01442@beta.informatik.hu-berlin.de>
On May 7, 9:58am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Re: cvs completion does not support partial path compl
}
} Bart Schaefer wrote:
}
} > 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?
}
} I normally use a sigle space, but that still results in a `-X desc'
} option passed to the action.
Yes, which results in things like
No match for ` ', `file', or `directory'
} If you don't want that, we could probably special-case that single space
} to mean to not pass a -X.
Either that, or strip all leading/trailing whitespace from the message,
and ignore empty messages.
--
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-07 14:54 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
2001-05-07 7:58 ` Sven Wischnowsky
2001-05-07 14:52 ` Bart Schaefer [this message]
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=1010507145218.ZM27680@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).