From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Eugenio Bargiacchi <svalorzen@gmail.com>, git@vger.kernel.org
Subject: Re: Better visual separation of hunks in `git add -p`
Date: Thu, 28 Mar 2024 11:21:20 -0700 [thread overview]
Message-ID: <xmqq1q7uusin.fsf@gitster.g> (raw)
In-Reply-To: <a9cffbe4aadd319760635ca6d5b4f465@manjaro.org> (Dragan Simic's message of "Thu, 28 Mar 2024 19:14:22 +0100")
Dragan Simic <dsimic@manjaro.org> writes:
> Here's a possible solution, or better said a new configuration option,
> which I've been thinking about for a while... When running "add -p",
> displayed chunks can sometimes become confusing or a bit hard on the
> eyes, but simply clearing the screen _before_ displaying any new step
> (i.e. a new chunk, interactive help, etc.) could make it much easier
> on the eyes. It would be a new option, of course.
Or your 'p' option can have a 'P' variant that clears before prints.
I have this feeling that even those who want clearing of the screen,
they do not want it always on, when many of their hunks are 7 lines
long.
next prev parent reply other threads:[~2024-03-28 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:36 Better visual separation of hunks in `git add -p` Eugenio Bargiacchi
2024-03-28 16:50 ` Junio C Hamano
2024-03-28 17:10 ` Eugenio Bargiacchi
2024-03-28 18:14 ` Dragan Simic
2024-03-28 18:21 ` Junio C Hamano [this message]
2024-03-28 18:29 ` Dragan Simic
2024-03-28 19:01 ` Eugenio Bargiacchi
2024-03-28 19:04 ` Dragan Simic
2024-03-28 19:08 ` Eugenio Bargiacchi
2024-03-28 19:16 ` Dragan Simic
2024-03-28 20:43 ` Junio C Hamano
2024-03-28 21:19 ` Dragan Simic
2024-03-28 21:43 ` Eugenio Bargiacchi
2024-03-28 21:49 ` Dragan Simic
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=xmqq1q7uusin.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=svalorzen@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 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.