From: "Shawn O. Pearce" <spearce@spearce.org>
To: sverre@rabbelier.nl
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: git gui: Possible to see which commands are executed?
Date: Tue, 20 May 2008 16:31:53 -0400 [thread overview]
Message-ID: <20080520203153.GH29038@spearce.org> (raw)
In-Reply-To: <bd6139dc0805201322r6c8dae8cy45d31af6c25fd25a@mail.gmail.com>
Sverre Rabbelier <alturin@gmail.com> wrote:
> >
> > That is probably difficult. Some of the code internally is more
> > about stringing the right sequence of plumbing together than it
> > is about a particular user action. I think it would take a bit of
> > work to make it do this, and I just don't see a reason to do it.
>
> The reason would be to make the switch from using git-gui only to
> using the commandline too... the again, it'd be cutting your own hand
> (or is it "throat" in English...) to make that transition easier.
I'm not worried about users leaving git-gui. Hell, if git-gui
was just git on training wheels and all git users left git-gui
after a while for the command line that would be telling as it
says the graphical interface is not desired. Or that git-gui's
interface is not well suited to the task.
Far from it. Some users like git-gui for its ability to show
the modified files, and let you stage/unstage individual hunks.
Others like its ability to perform checkout+pull in one mouse
click. Many like to point at things with a rodent than to use
the keyboard and enter (to them) isoteric commands.
Right now there are really only two git GUIs; git-gui and QGit.
Each has its strengths. Maybe this time next year we will have
a 3rd; name yet to be determined but it would come out of the
egit/jgit project as a stand-alone SWT/Java based Git UI.
> > CVS clients that show CVS commands can easily do so, because they
> > are directly executing the commands they show you. This is likely
> > also true of SVN commands. But git-gui on Git, that's a whole
> > different animal.
>
> Ah, I didn't realise git-gui does stuff that you can't really do
> through the regular porcelain. In that case it would indeed be
> impossible to print the regular porcelain commands. I think the
> '--trace' option should be advertised as 'debugging option' so that
> the user can see what is going on in the case something goes wrong
> perhaps?
Yes. I'll send Junio a patch for Documentation/git-gui.txt and
describe it as a debugging option, and also mention that the commands
it displays aren't all meant to be invoked by mortals.
--
Shawn.
next prev parent reply other threads:[~2008-05-20 20:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 12:03 git gui: Possible to see which commands are executed? Dirk Süsserott
2008-05-18 12:13 ` Miklos Vajna
2008-05-18 12:34 ` Dirk Süsserott
2008-05-19 2:21 ` Shawn O. Pearce
2008-05-20 19:03 ` Dirk Süsserott
2008-05-20 19:44 ` Shawn O. Pearce
2008-05-20 20:05 ` Sverre Rabbelier
2008-05-20 20:17 ` Shawn O. Pearce
2008-05-20 20:22 ` Sverre Rabbelier
2008-05-20 20:31 ` Shawn O. Pearce [this message]
2008-05-20 20:46 ` Sverre Rabbelier
2008-05-20 21:34 ` Junio C Hamano
2008-05-21 2:41 ` Shawn O. Pearce
2008-05-21 8:30 ` Johannes Schindelin
2008-05-21 9:27 ` Karl Hasselström
2008-05-22 12:12 ` Shawn O. Pearce
2008-05-22 20:55 ` Nigel Magnay
2008-05-22 23:05 ` Shawn O. Pearce
2008-05-20 20:12 ` Dirk Süsserott
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=20080520203153.GH29038@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newsletter@dirk.my1.cc \
--cc=sverre@rabbelier.nl \
/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).