[PATCH RFC] clone: copy hgrc paths if source and dest are local
peter.arrenbrecht at gmail.com
Mon Jun 14 04:07:10 CDT 2010
On Mon, Jun 14, 2010 at 10:51 AM, Adrian Buehlmann <adrian at cadifra.com> wrote:
> On 14.06.2010 08:48, Peter Arrenbrecht wrote:
>> On Sun, Jun 13, 2010 at 8:13 PM, Adrian Buehlmann <adrian at cadifra.com> wrote:
>>> If I am inside a mercurial clone (opened in my GUI), I don't want to
>>> have the TortoiseHg paths in scope, i.e. the UI shouldn't show me the
>>> TortoiseHg paths if I open the list of defined paths.
>> Just an idea: We add a [groups] setting to .hg/hgrc, and this causes
>> hg to also read ~/.hgrc.x for every x in [groups], containing
>> per-group overrides for ~/.hgrc. Then we make local clones copy the
>> [groups] setting. This might also be a solution for what I once
>> attempted to solve by having hg go back the parent dir hierarchy
>> looking for .hgrc.defaults files. Or we use a single group=x setting
>> to keep this simpler and use include files in ~/.hgrc.x instead if we
>> need composable aspects in .hgrc.
> Thanks for the idea. Perhaps we can avoid introducing yet more config files.
> How about defining a new section [pathgroups] (or just take the name
> [groups] for it, dunno).
Having proper config files would support configuring more than just
paths. For instance things like:
To name just a few that come to mind.
More information about the Mercurial-devel