git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git help -w should not create nohup.out
Date: Fri, 8 Feb 2008 14:25:43 +0300	[thread overview]
Message-ID: <20080208112543.GV30368@dpotapov.dyndns.org> (raw)
In-Reply-To: <200802080637.04015.chriscool@tuxfamily.org>

On Fri, Feb 08, 2008 at 06:37:03AM +0100, Christian Couder wrote:
> 
> I think I was worried about something like this:
> 
> 1) ssh -Y other_machine
> 2) git help -w, it opens my browser
> 3) open many other tabs in the browser
> 4) exit other_machine, oops my browser with all my tabs is gone

It seems to me that the browser will be killed anyway if ssh connection
is closed. At least, that what happened when I used ssh -Y localhost. In
fact, "nohup" made only easier to kill the browser in this way:
ssh -Y localhost
git help -w
exit
CTRL-C

Without "nohup" CTRL-C had no effect, but when I started the browser
with nohup then the connection would be closed and the browser killed.


Dmitry

  reply	other threads:[~2008-02-08 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08  1:33 [PATCH] git help -w should not create nohup.out Dmitry Potapov
2008-02-08  1:55 ` Johannes Schindelin
2008-02-08  3:40   ` Junio C Hamano
2008-02-08  5:37     ` Christian Couder
2008-02-08 11:25       ` Dmitry Potapov [this message]
2008-02-08 10:33     ` Dmitry Potapov
2008-02-08 20:36     ` [PATCH] remove "nohup" from git-help--browse Dmitry Potapov
2008-02-09  5:53       ` Christian Couder
2008-02-09 20:03         ` Dmitry Potapov
2008-02-10  2:02           ` Junio C Hamano
2008-02-10  2:06             ` Johannes Schindelin

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=20080208112543.GV30368@dpotapov.dyndns.org \
    --to=dpotapov@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).