All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jurko Gospodnetiii <jurko.gospodnetic@docte.hr>
Cc: git@vger.kernel.org
Subject: Re: Running git gui on Windows.
Date: Sun, 27 Jul 2008 08:02:44 -0700	[thread overview]
Message-ID: <20080727150244.GA7687@spearce.org> (raw)
In-Reply-To: <g6huoj$9rh$1@ger.gmane.org>

Jurko Gospodnetiii <jurko.gospodnetic@docte.hr> wrote:
>>   Is there a way to run git gui on Windows so it does not block the  
>> calling process?

In traditional UNIX shells this is "git gui &", requesting that the
shell background the process, but still monitor it for exit status.
On Windows there is no such easy concept.

>   I now realized my question did not say exactly what I intended it to.  
> I know I can start 'git gui' using:
>
>   start "" /b cmd /c git gui
>
>   from the command prompt and get the desired effect. I was wondering  
> why git gui does not do this in the first place and whether it could be  
> modified so that this is the default behaviour?

git-gui and gitk won't automatically background themselves, as they
are primarily developed on UNIX and have a UNIX like interface to
them, including backgrounding behavior.

We could add a -f flag to git-gui, such that "git gui -f" causes it
to fork+exec a new wish process, completely disconnecting it from the
calling shell.  (-f stolen from OpenSSH's ssh -f host xterm example)
I'd accept a patch for it, but its not high on my list of things to
write and debug myself.

-- 
Shawn.

      reply	other threads:[~2008-07-27 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27 13:48 Running git gui on Windows Jurko Gospodnetić
2008-07-27 13:55 ` Jurko Gospodnetić
2008-07-27 15:02   ` Shawn O. Pearce [this message]

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=20080727150244.GA7687@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jurko.gospodnetic@docte.hr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.