monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] add non-recursive by default (and option preferences ge


From: Daniel Carosone
Subject: [Monotone-devel] add non-recursive by default (and option preferences generally)
Date: Sat, 4 Nov 2006 13:09:58 +1100
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, Nov 02, 2006 at 06:31:41PM -0600, Timothy Brownawell wrote:
> I've committed changes that do this

I remain... unconvinced.. about add being non-recursive by default.

My personal preference is certainly that is *is* recursive, even if
that preference just means my fingers learn to type a couple of extra
chars.

Rather than being overly pedantic about defaults and preferences, this
brings up something I've thought about a few times before.  CVS has a
.cvsrc file that allows the user to set their own "default options"
for each subcommand: "update -dP" or "diff -u" to take a couple of
examples from mine.  It would be nice to have something equivalent.

Rather than adding extra things to _MTN/options, the fully generic
monotone equivalent would be a set of command hooks (similar to the
attr hooks), one per command.  These would be invoked at the
appropriate point, and would have the opportunity to manipulate the
options before execution.

It might work on the raw string, early, or on a more structured view
of the options, post parsing.  Is there a convenient point with the
new bpo framework to prepare a structured representation of the
command line for lua, and invoke a hook, before evaluating the
(possibly adjusted) options?

--
Dan.

Attachment: pgpH68gXNNiiG.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]