Re: [Monotone-devel] [PATCH] parent selector 'p:xxx'

[Daniel Carosone]

On Sun, Oct 07, 2007 at 09:58:14PM -0600, Derek Scherger wrote:
> Ethan Blanton wrote:
> 
> > I believe that it should; if it is more than just a few columns wide,
> > it tends to make diffs and commit messages wrap on terminals they are
> > meant to accommodate, and it displays an unfortunate tendency to be
> > far more than a "few" columns wide.  Even when it is correct, for
> > Pidgin it often has 3-5 parallel lines at two columns apiece, and
> > often it mistakenly draws O(a lot) of parallel lines.
> 
> Another thought. Maybe what we really need is something like .csvrc
> where you can specify the default options that you generally want with
> specific commands. I'm not sure how you would occasionally un-set
> options that were set like this though.

An option for this we dscussed (at the summit, I think) was a lua
construct.  Something that was invoked as a hook early, passed a table
of the (tokenised, or partially parsed into options and their paired
argument values?) command line, and given the opportunity to adjust
the table before execution proceeds.  Insert or remove options, modify
arguments, etc etc.

This would be a place where you could implement private command
aliases and shortcuts, favourite branch name expansions, set or unset
default options with as much context/command sensitivity as you feel
like, and anything else you care to dream up. That's the basic form.

Some simple way to chain these so that global, user- and workspace-
specific versions could all be invoked, would also be cool.

A more complex form (to implement, not for the user) would build up a
table of match expressions and substitutions/actions from individual
items, perhaps in a more .cvsrc-like file (a little like how
.mtn-ignore is parsed and added to the hook's table).

--
Dan.

pgpDtmF3EZYtf.pgp
Description: PGP signature