git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git_getpass regression?
Date: Tue, 3 Jul 2012 13:11:22 -0400	[thread overview]
Message-ID: <20120703171121.GA3294@sigill.intra.peff.net> (raw)
In-Reply-To: <CABPQNSZGcReC4CgaYcmwsXyGSqzQgHKQceZ2M5D=zQmyAs8_Ug@mail.gmail.com>

On Tue, Jul 03, 2012 at 06:28:11PM +0200, Erik Faye-Lund wrote:

> Is there some other way of getting EOF from the console than Ctrl+C?
> If not, perhaps we can disable the Ctrl+C handling altogether for the
> current process, and restore the console mode on EOF? That only leaves
> the "Bash kills our process"-case, but Bash seems to set a sane
> console mode anyway.

On unix systems, you can generally send EOF on a terminal using Ctrl+D
(and strbuf_getline should handle it properly).  I have no clue if that
works on a Windows console, though. Also, I wonder if these kind of
terminal issues are different based on the terminal emulator you are
using (e.g., msys bash window versus something like pterm).

-Peff

  reply	other threads:[~2012-07-03 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 10:06 git_getpass regression? Erik Faye-Lund
2012-06-29 17:39 ` Jeff King
     [not found]   ` <CABPQNSZ4NhEA1CBiCBD_YNJZcnK8u=NtQ3PeDa5c0NDROPDyrQ@mail.gmail.com>
2012-06-29 20:30     ` Jeff King
2012-06-30 11:27       ` Erik Faye-Lund
2012-06-30 18:36         ` Jeff King
     [not found]           ` <CABPQNSYP6mUZb-1dCifytRxqP7_grzYzON2bjevK2zsGawb-yg@mail.gmail.com>
2012-07-03 16:28             ` Erik Faye-Lund
2012-07-03 17:11               ` Jeff King [this message]
2012-07-03 17:37                 ` Erik Faye-Lund
2012-07-18  5:53                   ` Junio C Hamano
2012-07-18 14:23                     ` Erik Faye-Lund

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=20120703171121.GA3294@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=kusmabite@gmail.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).