From: lars.schneider@autodesk.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, sbeller@google.com, sunshine@sunshineco.com,
kaartic.sivaraam@gmail.com, sandals@crustytoothpaste.net,
peff@peff.net, Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v5 0/2] launch_editor(): indicate that Git waits for user input
Date: Thu, 7 Dec 2017 16:16:39 +0100 [thread overview]
Message-ID: <20171207151641.75065-1-lars.schneider@autodesk.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
Hi,
Patch 1/2: No change. The patch got "looks good to me" from Peff [1]
Patch 2/2: I changed the waiting message to our bikeshedding result [2] and
I enabled the waiting message on dumb terminals for consistency.
I also tested the patch on OS X and Windows with smart and dumb terminals.
Thanks for the reviews,
Lars
[1] https://public-inbox.org/git/20171130203042.GB3313@sigill.intra.peff.net/
[2] https://public-inbox.org/git/20171204220908.GA8184@sigill.intra.peff.net/
RFC: https://public-inbox.org/git/274B4850-2EB7-4BFA-A42C-25A573254969@gmail.com/
v1: https://public-inbox.org/git/xmqqr2syvjxb.fsf@gitster.mtv.corp.google.com/
v2: https://public-inbox.org/git/20171117135109.18071-1-lars.schneider@autodesk.com/
v3: https://public-inbox.org/git/20171127134716.69471-1-lars.schneider@autodesk.com/
v4: https://public-inbox.org/git/20171129143752.60553-1-lars.schneider@autodesk.com/
Base Ref: master
Web-Diff: https://github.com/larsxschneider/git/commit/c00d4de8cf
Checkout: git fetch https://github.com/larsxschneider/git editor-v5 && git checkout c00d4de8cf
### Interdiff (v4..v5):
diff --git a/editor.c b/editor.c
index cdad4f74ec..d52017363c 100644
--- a/editor.c
+++ b/editor.c
@@ -45,11 +45,17 @@ int launch_editor(const char *path, struct strbuf *buffer, const char *const *en
const char *args[] = { editor, real_path(path), NULL };
struct child_process p = CHILD_PROCESS_INIT;
int ret, sig;
- int print_waiting_for_editor = advice_waiting_for_editor &&
- isatty(2) && !is_terminal_dumb();
+ int print_waiting_for_editor = advice_waiting_for_editor && isatty(2);
if (print_waiting_for_editor) {
- fprintf(stderr, _("hint: Waiting for your editor input..."));
+ 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);
}
@@ -71,11 +77,10 @@ int launch_editor(const char *path, struct strbuf *buffer, const char *const *en
return error("There was a problem with the editor '%s'.",
editor);
- if (print_waiting_for_editor)
+ if (print_waiting_for_editor && !is_terminal_dumb())
/*
- * go back to the beginning and erase the
- * entire line to avoid wasting the vertical
- * space.
+ * Go back to the beginning and erase the entire line to
+ * avoid wasting the vertical space.
*/
fputs("\r\033[K", stderr);
}
### Patches
Lars Schneider (2):
refactor "dumb" terminal determination
launch_editor(): indicate that Git waits for user input
Documentation/config.txt | 3 +++
advice.c | 2 ++
advice.h | 1 +
cache.h | 1 +
color.c | 3 +--
editor.c | 29 +++++++++++++++++++++++++++--
sideband.c | 5 ++---
7 files changed, 37 insertions(+), 7 deletions(-)
base-commit: 89ea799ffcc5c8a0547d3c9075eb979256ee95b8
--
2.15.1
next reply other threads:[~2017-12-07 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 15:16 lars.schneider [this message]
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
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=20171207151641.75065-1-lars.schneider@autodesk.com \
--to=lars.schneider@autodesk.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=larsxschneider@gmail.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).