Re: [Monotone-devel] mtn automate evolution, part 2: workspace query

[Ben Walton]

I have a mostly completed set_option that might meet this need.  I
hadn't placed it in the automate group of functions, but rather the
general workspace set.  Would it be better placed in automate?

-Ben

On 12/19/06, Thomas Keller <address@hidden> wrote:
> Christof Petig schrieb:
> > What about
> >
> > $ mtn automate get_workspace
> > database  "/usr/local/lib/monotone.db"
> >   branch  "net.venge.monotone.cvssync.refactor"
> >   keydir  "/home/christof/.monotone/keys"
> >      key  "address@hidden"
> > workspace "/home/christof/projects/monotone"
>
> mtn automate get_option already reads individual entries out of
> _MTN/options, though one could argue if your version is more practical
> than get_option since one probably reads more than just one option at a
> time anyways.
> On the other hand, get_option could be nicely symmetric to a not yet
> existing set_option to override workspace defaults. Opinions?
>
> Thomas.
>
> --
> ICQ: 85945241 | SIP: 1-747-027-0392 | http://www.thomaskeller.biz
> > Guitone, a frontend for monotone: http://guitone.berlios.de
> > Music lyrics and more: http://musicmademe.com
>
>
> _______________________________________________
> Monotone-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/monotone-devel


--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <address@hidden>

Unanswered questions are far less dangerous than unquestioned answers.
- The Roadside Pulpit
---------------------------------------------------------------------------------------------------------------------------