[PATCH 3 of 5] shelve: use an --unshelve parameter instead of a command

Antoine Pitrou solipsis at pitrou.net
Fri Sep 20 00:55:58 CDT 2013

On Thu, 19 Sep 2013 23:34:55 +0200
Martin Geisler <martin at geisler.net> wrote:
> Augie Fackler <raf at durin42.com> writes:
> > On Wed, Sep 18, 2013 at 09:31:51PM -0700, Siddharth Agarwal wrote:
> >> On 09/18/2013 09:29 PM, David Soria Parra wrote:
> >> >I used an parameter --unshelve instead of a command due to the
> >> >previous discussion on the extension. I personally don't have a
> >> >preference, but it was suggested that we don't use an "unshelve"
> >> >command. This way all the parameters are defined on the same
> >> >command. Would you prefer "--apply" maybe?
> >> >
> >> >Matt and rest: Any suggestions on the UI bits?
> >>
> >> I'd prefer unshelve too.
> >
> > I think I would too, but [alias] unshelve = shelve --unshelve is
> > pretty easy,
> It is easy, but only some users will discover the alias functionality
> and only some of them will think of adding an alias.
> I like my software to come with good defaults -- I actually don't like
> changing it too much from those defaults. Partly because I like to think
> that there is an integrity to the system that I may disturb and partly
> because those customizations don't automatically move with me to other
> systems.

Another reason is to make Mercurial easier to teach. "Ok, Mercurial
doesn't have an unshelve command, but you can emulate it by defining an
alias there in your .hgrc" is a pretty pointless distraction.

(also, the average user will actually never define any aliases, they
will just keep pestering against the tool)



More information about the Mercurial-devel mailing list