Re: more pedantry -- to recurse or not to recurse?

On Mon, Nov 01, 2004 at 01:06:57PM -0500, Robert P. J. Day wrote:
>   i think it's too bad that the global "-r" option was used to select
> a directory.  thinking out loud, it might have been more consistent to
> use global options like:
> 
>   -R		change to repo root first
>   -d <dir>	change to <dir> first (*must* have <dir> arg)
> 		and current directory as default in all cases
>   -r		work recursively (if recursion is *not* the default)
>   -l		work locally (non-recursively) if recursive *is*
> 		the default
> 
> but the current usage is undoubtedly already cast in stone so, as i
> said, just thinking out loud.

As long as we are thinking aloud, it annoys me that the bk options
(apparently) aren't parsed with getopt(), so bk does not allow an
optional space between the option letter and its argument.  I had to
train my fingers to work differently for bk vs. almost any other
command.

Ah, I feel better now that I got that off my chest.

Anyway, there is a way to sanitize the recursive options and the space
thingy, for those of us that care, while not breaking anything that
came before.  That would be to invent an environment variable that if
set to some value, would cause the commands to operate more like we
expect them to.

-Rick

-- 
Rick Richardson  [email protected]    http://home.mn.rr.com/richardsons/
Linux tools for geocaching          http://geo.rkkda.com

"your new name should be "lindos" and your slogan should be "because
it's the W that is causing all the problems."
    -- Anonymous Lindows customer
_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.