From: Philip Martin <philip@codematters.co.uk>
To: Julian Foad <julianfoad@btopenworld.com>
Cc: dev@subversion.tigris.org, Sebastien Cevey <seb@cine7.net>,
Clint Adams <clint@zsh.org>,
zsh-workers@sunsite.dk
Subject: Re: [PATCH] bash_completion: improvement, fixes and tests [was: Re: subversion and programmable completion]
Date: Wed, 23 Jul 2003 22:27:29 +0100 [thread overview]
Message-ID: <87u19dorwe.fsf@codematters.co.uk> (raw)
In-Reply-To: <3F1EE28F.50500@btopenworld.com> (Julian Foad's message of "Wed, 23 Jul 2003 20:31:27 +0100")
Julian Foad <julianfoad@btopenworld.com> writes:
> # Print the valid subcommands for "svn", one per line, sorted.
> # Usage: get_svn_subcommands
> get_svn_subcommands() {
> svn help |
> # Find the relevant lines;
> # remove brackets and commas; put each word on its own line.
> sed -n -e '1,/^Available subcommands:$/d;/^$/q' \
> -e 's/[ )]//g;s/[(,]/\n/g;p' |
> sort
> }
[...]
> echo "Checking list of subcommands"
> HELP_SUBCMDS=`get_svn_subcommands | tr "\n" " "`
At this point "echo $HELP_SUBCMDS" gives
add cat checkoutnco cleanup commitnci copyncp deletendelnremovenrm diffndi export helpn?nh import info listnls log merge mkdir movenmvnrenamenren propdelnpdel propeditnpeditnpe propgetnpgetnpg proplistnplistnpl propsetnpsetnps resolve revert statusnstatnst switchnsw updatenup
$ sed -V | head -1
GNU sed version 3.02
$ echo 'x(y' | sed 's/[(,]/\n/g'
xny
--
Philip Martin
next prev parent reply other threads:[~2003-07-23 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 16:27 subversion and programmable completion Clint Adams
2003-07-21 15:15 ` kfogel
2003-07-21 22:48 ` Clint Adams
2003-07-21 18:33 ` Sebastien Cevey
2003-07-21 22:52 ` Clint Adams
2003-07-23 19:31 ` [PATCH] bash_completion: improvement, fixes and tests [was: Re: subversion and programmable completion] Julian Foad
2003-07-23 21:27 ` Philip Martin [this message]
2003-07-24 1:29 ` Julian Foad
2003-07-24 5:46 ` Philip Martin
2003-08-18 9:24 ` Roman Neuhauser
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=87u19dorwe.fsf@codematters.co.uk \
--to=philip@codematters.co.uk \
--cc=clint@zsh.org \
--cc=dev@subversion.tigris.org \
--cc=julianfoad@btopenworld.com \
--cc=seb@cine7.net \
--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).