On Sat, Oct 29, 2011 at 03:11, Adam Spiers vcs-h...@adamspiers.org wrote:
By you are you referring to me or Joey? Yes, my intention
was that ~/.git-repos contains all git repos (or at least most).
Yes, sorry for the confusion.
If you mean, every repo *contains* its own .mrconfig, then
I
On Sat, Oct 29, 2011 at 2:11 PM, Richard Hartmann
richih.mailingl...@gmail.com wrote:
On Sat, Oct 29, 2011 at 03:11, Adam Spiers vcs-h...@adamspiers.org wrote:
I like that scheme with things like apache (sites-available
vs. sites-enabled) although with mr config, the same effect can by
If I have multiple repository paths all similar but spread across
different .mrconfig files, e.g.
in ~/.mrconfig
[.config/mr]
checkout = ...
in ~/.config/mr/config.d/CLI:
[$HOME/.git-repos/zsh]
...
[$HOME/.git-repos/mutt]
...
and in ~/.config/mr/config.d/GUI:
On Fri, 28 Oct 2011 16:42:16 +0100, Adam Spiers vcs-h...@adamspiers.org wrote:
If I have multiple repository paths all similar but spread across
different .mrconfig files, e.g.
in ~/.mrconfig
[.config/mr]
checkout = ...
in ~/.config/mr/config.d/CLI:
Adam Spiers wrote:
If I have multiple repository paths all similar but spread across
different .mrconfig files, e.g.
in ~/.mrconfig
[.config/mr]
checkout = ...
in ~/.config/mr/config.d/CLI:
[$HOME/.git-repos/zsh]
...
[$HOME/.git-repos/mutt]
...
and in
On Fri, Oct 28, 2011 at 5:40 PM, Pieter Praet pie...@praet.org wrote:
However this doesn't work - I'm guessing that variable expansion in
the section headers is done in Perl, so is not influenced by the
shell-code in the DEFAULT lib?
So is there any other way of avoiding this duplication?
On Fri, Oct 28, 2011 at 8:03 PM, Richard Hartmann
richih.mailingl...@gmail.com wrote:
On Fri, Oct 28, 2011 at 18:45, Joey Hess j...@kitenet.net wrote:
mr can look much nicer if you take advantage of locality and chaining.
By locality, I mean putting a mrconfig close to the directories it
