On Sat, Jan 5, 2019 at 4:17 PM Arne Babenhauserheide <[email protected]> wrote: > Ludovic Chabant <[email protected]> writes: > >> Did anything changed in hg policy to add non-interactive key/value > >> modification for config from command line? > > > So I guess at this point nobody wants to go down that path knowing that it > > will most likely be a huge time sink of code maintenance and feature bloat. > > Plus, there's a fair amount of people who think that .hgrc is meant to be > > written by a human. > > Also with `hg config -el` the need for that is reduced a lot.
Do you mean "echo commands | EDITOR='interp 3<&0 /dev/fd/3 < ' hg config -l"? :P TBH, I've not understood the need for config --edit. Is there a use-case not already satisfied by "editor ~/.hgrc" or "cd somewhere; editor .hg/hgrc"? Is either of those difficult enough to warrant special commands? _______________________________________________ Mercurial mailing list [email protected] https://www.mercurial-scm.org/mailman/listinfo/mercurial
