git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gauthier Östervall" <gauthier@ostervall.se>
To: unlisted-recipients:; (no To-header on input)
Cc: git <git@vger.kernel.org>
Subject: Re: Command-line git Vs IDE+plugin?
Date: Wed, 4 Dec 2013 10:56:51 +0100	[thread overview]
Message-ID: <CAM8gEgi1+4EYXAMzHxWbh0qZiFWGSU52fLKSeiPS-O3Uk5ifgw@mail.gmail.com> (raw)
In-Reply-To: <vpq1u2c9ukx.fsf@anie.imag.fr>

On Tue, Nov 19, 2013 at 6:20 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> One thing the command-line does well is to give names to concepts
> (basically, command names, option names, ...). It's easy to write in a
> tutorial or an email "run the command 'git foo'". It's less easy to
> write "click on that red button, on the right of the green one".

And it is also easier for many to press a button than writing a
command. This is a bad thing, in my experience. In a GUI, people tend
to take chances: "Oh, reset, that sounds like what I want. What, it
did not work? Oh there is this option 'hard', let's tick it and see
what happens."

Another thing GUIs do not (often) offer is history. I would be lost if
I couldn't see what I was trying to do 5 commands ago (before someone
interrupted me), or refer to a previous error message.

But if you cannot touch-type, buttons are going to be more attractive.

  reply	other threads:[~2013-12-04  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 17:11 Command-line git Vs IDE+plugin? Matthieu Moy
2013-11-18 17:42 ` Philippe Vaucher
2013-11-18 18:46   ` Matthieu Moy
2013-11-19  9:53   ` Konstantin Khomoutov
2013-11-18 17:47 ` Andreas Krey
2013-11-19 12:36 ` Thomas Koch
2013-11-19 16:53   ` Junio C Hamano
2013-11-19 17:20     ` Matthieu Moy
2013-12-04  9:56       ` Gauthier Östervall [this message]
2013-11-19 16:55   ` Keshav Kini
2013-11-19 12:45 ` Noufal Ibrahim KV
2013-12-04 11:10 ` Chris Packham

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM8gEgi1+4EYXAMzHxWbh0qZiFWGSU52fLKSeiPS-O3Uk5ifgw@mail.gmail.com \
    --to=gauthier@ostervall.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.
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 NNTP newsgroup(s).