Hi *, sorry for the extreme late reply... Anyway, I created a patch which hopefully resolves my issues while not reintroducing any of the old ones. Dan Nicolaescu wrote: > Sascha Wilde writes: [...] > Setting HGRCPATH was the result of some discussion on the list (here or > the bug list). > > We want to be able to reliably parse the results of hg log regardless > of the users .hgrc settings. In case my attached patch (re)creates any of the problems discussed back then I would be grateful for a pointer to the thread in question. >> So at the moment it looks as if the HGRCPATH='' can be simply removed! > > What happens if the user changes the format of hg log in her .hgrc ? I see only two possible ways how this could happen: alias definitions (also redefining the original command name is discouraged) and default definitions (currently repriced in favor for aliases). My patch addresses them both... >> But there might be some other reasons (Bug#5846 seems to indicate that) >> besides the localization issue for trying to deactivate .hgrc files... As said before: localization is orthogonal to hgrc. And the problem described in the second part of Bug#5846 was really due to the -- meanwhile fixed -- use of an abbreviated hg command in vc-hg-working-revision. So all problems reported in Bug#5846 should stay fixed with my proposed patch. Chong Yidong wrote: > Sascha Wilde writes: >> Maybe Chong Yidong knows some details, as he made the last changes to >> the code in question? > > See Bug#5960. Sorry, but neither does Bug#5960 mention hgrc nor does the related patch include the hgrc related part. So here is my patch, I successfully tested it with an "evil" hgrc redefining 'log' and 'parents'. It would be great if it could be committed to get some wider testing...