Excerpts from Denis Laxalde's message of 2017-03-23 10:14:14 +0100: > Ryan McElroy a écrit : > > On 3/22/17 7:29 AM, Sean Farley wrote: > >> Yuya Nishihara <y...@tcha.org> writes: > >> > >>> On Sun, 12 Mar 2017 21:38:00 -0700, Gregory Szorc wrote: > >>>> # HG changeset patch > >>>> # User Gregory Szorc <gregory.sz...@gmail.com> > >>>> # Date 1489378362 25200 > >>>> # Sun Mar 12 21:12:42 2017 -0700 > >>>> # Node ID d30057d358076cbe7d632cd573095af97543f932 > >>>> # Parent 1c3352d7eaf24533ad52d4b8a024211e9189fb0b > >>>> show: new extension for displaying various repository data > >>> The idea sounds nice to me. I just checked minor implementation details > >>> about formatter. > >> Just a quick reply (as I whittle down my backlog), but a lot of people > >> (including myself) have a 'show' alias (inspired by 'git show'). > >> > >> That may or may not be a factor in this. > > > > Greg called this out specifically in his excellent summary. > > > > FB also has a "show" extension that replaced our "show" alias: > > https://bitbucket.org/facebook/hg-experimental/src/default/hgext3rd/show.py > > It seems to me that all "show" extensions/aliases can be replaced by the > proposed extension. Also if we look to the future, it seems to me that
The problem is top-level command names are rare resources. It's really hard to name things. I think subcommands is a great choice. > we'd have hard time to explain that this command is not called "show" > because there used to be extensions/aliases with this name and that got > replaced by said command. Another benefit of the "show" approach is it's supposed to be read-only. It feels cleaner than for example "hg bookmark" which could do either read or write. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel