git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13:43:21 -0700	[thread overview]
Message-ID: <xmqqr0fut7di.fsf@gitster.g> (raw)
In-Reply-To: <de182310842ea3ff04c171a271587ca1@manjaro.org> (Dragan Simic's message of "Thu, 28 Mar 2024 20:16:28 +0100")

Dragan Simic <dsimic@manjaro.org> writes:

> Of course, users could pick the right escape sequences for their
> terminals, but as you already noted, the same configurations could
> end up being used on different terminals.  For example, even SSHing
> into a machine using a different SSH client could lead to a mess.

There is a separate discussion of conditional configuration based on
environment variable settings, e.g.

    [includeIf "env:TERM:vt100"]
	path = ~/.git-config-bits/vt100

where the named file might have

    [prompt] prefix = "\033[H\033[J"

so it is certainly doable.

It is a different story if doing so is sensible, of course.






  reply	other threads:[~2024-03-28 20:43 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
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 [this message]
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=xmqqr0fut7di.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 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).