Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: _bzr

X-seq: zsh-workers 22391
From: Clint Adams <clint@xxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: PATCH: _bzr
Date: Tue, 28 Mar 2006 19:04:19 -0500
In-reply-to: <20060328230759.GG8106@xxxxxxxxxxxxx>
Mail-followup-to: zsh-workers@xxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20050906160630.GA10503@xxxxxxxxxxx> <5740.1126261568@xxxxxxxxxxxxxxxxxxxxxxx> <20050909134846.GA22966@xxxxxxxxxxx> <20060328230759.GG8106@xxxxxxxxxxxxx>

> Since many of you folks are much better at completion functions than me,
> please feel free to give it a look and see if it can't be improved even
> more.  I'll attach it to this message to make it easy to review...

In case anyone else is interested in this, the original intent of the
bzr shell-complete subcmd was to output completion info for each
subcmd.  For example:

% bzr s-c add
--no-recurse
--dry-run
--verbose
file*

There was supposed to be some rewrite of the options parsing code to
allow shell-complete to output instead of 'file*', either a line that
could be passed directly to _arguments or something that could be
transformed easily.

Finishing this might be a fun project for someone who uses bzr and can
stand Python.

References:
- Re: PATCH: _bzr
  - From: Wayne Davison

Messages sorted by: Reverse Date, Date, Thread, Author