From: "Karl Hasselström" <kha@treskal.com>
To: Andreas Ericsson <ae@op5.se>
Cc: "David Kågedal" <davidk@lysator.liu.se>, git@vger.kernel.org
Subject: Re: Collection of stgit issues and wishes
Date: Wed, 13 Dec 2006 12:03:14 +0100 [thread overview]
Message-ID: <20061213110314.GA22670@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <457FD3E4.3090104@op5.se>
On 2006-12-13 11:20:20 +0100, Andreas Ericsson wrote:
> David Kågedal wrote:
>
> > "Catalin Marinas" <catalin.marinas@gmail.com> writes:
> >
> > > On 08/12/06, Yann Dirson <ydirson@altern.org> wrote:
> > >
> > > > - shortcuts (st -> status, etc.), possibly making use of the
> > > > git alias system ?
> > >
> > > Did this last night as it was pretty easy and without the GIT
> > > alias system (which I am not familiar with). The idea is that if
> > > it cannot find an exact match, it tries to look for all the
> > > commands starting with the passed argument. If more than one
> > > command is found, it reports an "ambiguous command".
> >
> > That approach can cause problems later on. If "stgit st" is
> > currently a unique prefix of "stgit status", people might use it
> > in scripts. Then, one day, you add the "stgit store" command, or
> > whatever, and their scripts start breaking for no good reason.
>
> People who use abbreviations of commands in scripts ought to be
> shot, not catered to, especially if they know this abbreviation is
> automagically calculated.
Well, yes, but there's no reason to not shoot them _politely_ ...
I'd prefer hand-picked command abbreviations to reduce namespace
clutter. That way, it's even possible to have "ambiguous" shortcuts --
for example, "stg st" -> "stg status" even if "stg store" exists. And
shortcuts that aren't prefixes, like "stg ua" -> "stg unapplied". And
the user doesn't need to retrain her fingers just because a prefix
gets ambiguous.
For prefixes, tab completion is a much better answer.
--
Karl Hasselström, kha@treskal.com
next prev parent reply other threads:[~2006-12-13 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 22:17 Collection of stgit issues and wishes Yann Dirson
2006-12-08 22:27 ` Jakub Narebski
2006-12-10 8:55 ` Jakub Narebski
2006-12-10 11:06 ` Jakub Narebski
[not found] ` <b0943d9e0612100831t7b79d4b1p436de5dbb813e51a@mail.gmail.com>
2006-12-10 17:01 ` Jakub Narebski
2006-12-10 22:26 ` Catalin Marinas
2006-12-10 23:02 ` Jakub Narebski
2006-12-10 23:24 ` Catalin Marinas
2006-12-10 23:37 ` Jakub Narebski
2006-12-11 12:59 ` Catalin Marinas
2006-12-21 11:39 ` Jakub Narebski
2006-12-11 18:41 ` Yann Dirson
2006-12-13 22:14 ` Catalin Marinas
2006-12-21 23:48 ` Jakub Narebski
2006-12-10 16:25 ` Catalin Marinas
2006-12-17 23:15 ` Yann Dirson
2006-12-12 9:43 ` Catalin Marinas
2006-12-12 10:02 ` Jakub Narebski
2006-12-13 7:22 ` David Kågedal
2006-12-13 10:20 ` Andreas Ericsson
2006-12-13 11:03 ` Karl Hasselström [this message]
2006-12-17 23:21 ` Yann Dirson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061213110314.GA22670@diana.vm.bytemark.co.uk \
--to=kha@treskal.com \
--cc=ae@op5.se \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).