From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lars Schneider <lars.schneider@autodesk.com>,
git@vger.kernel.org, sbeller@google.com, sunshine@sunshineco.com,
kaartic.sivaraam@gmail.com, sandals@crustytoothpaste.net,
peff@peff.net
Subject: Re: [PATCH v5 2/2] launch_editor(): indicate that Git waits for user input
Date: Thu, 7 Dec 2017 16:48:57 +0100 [thread overview]
Message-ID: <FCBDBD58-0593-4FFC-B574-61D67CAF13C6@gmail.com> (raw)
In-Reply-To: <xmqqr2s6ee7e.fsf@gitster.mtv.corp.google.com>
> On 07 Dec 2017, at 16:43, Junio C Hamano <gitster@pobox.com> wrote:
>
> lars.schneider@autodesk.com writes:
>
>> + if (print_waiting_for_editor) {
>> + fprintf(stderr,
>> + _("hint: Waiting for your editor to close the file... "));
>> + if (is_terminal_dumb())
>> + /*
>> + * A dumb terminal cannot erase the line later on. Add a
>> + * newline to separate the hint from subsequent output.
>> + */
>> + fprintf(stderr, "\n");
>> + fflush(stderr);
>> + }
>
> Was the trailing whitespace at the end of the hint message intended?
>
> If we expect the editor to spit out additional garbage on the line,
> it would probably help to have that SP,
Argh. I forgot to mention that in the cover letter. Yes, I added
the whitespace intentionally for exactly that reason.
> but if that is why we have it
> there, it probably should be done only when !is_terminal_dumb().
That, of course, is correct. My intention was to make the code simpler
but I can see that people would be confused about the whitespace.
How about this?
fprintf(stderr,
_("hint: Waiting for your editor to close the file..."));
if (is_terminal_dumb())
/*
* A dumb terminal cannot erase the line later on. Add a
* newline to separate the hint from subsequent output.
*/
fprintf(stderr, "\n")
else
fprintf(stderr, " ")
Can you squash that if you like it?
Thanks,
Lars
next prev parent reply other threads:[~2017-12-07 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 15:16 [PATCH v5 0/2] launch_editor(): indicate that Git waits for user input lars.schneider
2017-12-07 15:16 ` [PATCH v5 1/2] refactor "dumb" terminal determination lars.schneider
2017-12-07 15:16 ` [PATCH v5 2/2] launch_editor(): indicate that Git waits for user input lars.schneider
2017-12-07 15:43 ` Junio C Hamano
2017-12-07 15:48 ` Lars Schneider [this message]
2017-12-07 16:16 ` Lars Schneider
2017-12-07 16:30 ` Junio C Hamano
2017-12-07 16:36 ` Lars Schneider
2017-12-07 17:37 ` Kaartic Sivaraam
2017-12-07 17:56 ` Lars Schneider
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FCBDBD58-0593-4FFC-B574-61D67CAF13C6@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=lars.schneider@autodesk.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).