Yann Dirson wrote: > Hm, I'm not sure adding lines for each repo is a good idea (even > automatically).
I'm not either, really. Another option would be to list "checked out" mrconfig files in another file (~/.mrconfigs). > Oh, looks like I missed this option - it seems to provide exactly what > I need. That's good.. > > If you'd like to alias mr = mr -p > > Rather than that, what about adding support for making it the default > in ~/.mrconfig ? Well, not exactly that, since that would imply "read > ~/.mrconfig first, and then if this flag is specified, search for an > additional .mrconfig upstairs." - that would also match the behaviour > of other tools (like git's ~/.config and .git/config). mr does read ~/.mrconfig first. Something could be added, perhaps in the ALIAS section, to enable options by default. I'm not sure though, how this is better than shell aliases? > Well, couldn't the problem about trusting files be solved in a less > intrusive way ? I would suggest to refuse loudly to use a .mrconfig > with improper write permissions The issue is not really local write permissions, it is mrconfig files that others may edit via VCS. For example, I've proposed that d-i convert to git and use a toplevel mrconfig file to list all the git repositories. -- see shy jo
signature.asc
Description: Digital signature
