Re: something equivalent to "bk ls"?

"Robert P. J. Day" <[email protected]> Fri, 29 Oct 2004 05:19:15 -0400 (EDT)
Newsgroups gmane.comp.version-control.bitkeeper.user
Message-ID <[email protected]>
On Fri, 29 Oct 2004, Måns Rullgård wrote:

> Larry McVoy <[email protected]> writes:
>
> >> Well, just put
> >>
> >> _ls() {
> >>         find SCCS -name 's.*' | bk sfiles -g -
> >> }
> >>
> >> somewhere in bk.script.
> >
> > Excellent point but perhaps not well known.  In `bk bin`/bk.script you will
> > find a shell script (which is good reading, you should look at it).  Anything
> > which is added as a shell function that script as "_my_super_duper_feature"
> > will be run when you run "bk my_super_duper_feature".  Note that the shell
> > function has a leading underscore but the bk call does not.
> >
> > So you can add whatever feature you want to bk.script and have the big fun.
>
> Perhaps it would be an idea to always include something like
> ~/.bk/script to avoid changing the main bk.script.  It would also
> preserve these additions when upgrading bk.

i like this idea, but perhaps to be more general, a path-like variable
to collect multiple script files if you happen to have multiple
authors?  BKSCRIPTFILES?  or something like that?  perhaps with
~/.bk/scripts as a default but overrideable.  just thinking out loud.

rday