From: Pat Thoyts <patthoyts@users.sourceforge.net>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix use of hunk tag for non-hunk content.
Date: Mon, 06 Dec 2010 21:25:43 +0000 [thread overview]
Message-ID: <87ei9uy4o8.fsf@fox.patthoyts.tk> (raw)
In-Reply-To: <02730a5b5e904409da58c7f5ebe40e16e7adc1f1.1291019649.git.bert.wesarg@googlemail.com> (Bert Wesarg's message of "Mon, 29 Nov 2010 12:41:52 +0100")
Bert Wesarg <bert.wesarg@googlemail.com> writes:
>The hunk tag d_@ lost its blue forground color in "apply color information
>from git diff output" (2010-10-22, 8f85599). But this tag was also used
>for non-hunk content like untracked file mime types or git submodules.
>
>Introduce a new tag for this type of content which has the blue forground
>again.
>
>Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com>
>---
> git-gui.sh | 2 ++
> lib/diff.tcl | 14 +++++++-------
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
>diff --git a/git-gui.sh b/git-gui.sh
>index 38362fa..c85a53c 100755
>--- a/git-gui.sh
>+++ b/git-gui.sh
>@@ -3331,6 +3331,8 @@ foreach {n c} {0 black 1 red4 2 green4 3 yellow4 4 blue4 5 magenta4 6 cyan4 7 gr
> }
> $ui_diff tag configure clr1 -font font_diffbold
>
>+$ui_diff tag conf d_info -foreground blue -font font_diffbold
>+
> $ui_diff tag conf d_cr -elide true
> $ui_diff tag conf d_@ -font font_diffbold
> $ui_diff tag conf d_+ -foreground {#00a000}
>diff --git a/lib/diff.tcl b/lib/diff.tcl
>index 8fea947..8435635 100644
>--- a/lib/diff.tcl
>+++ b/lib/diff.tcl
>@@ -208,32 +208,32 @@ proc show_other_diff {path w m cont_info} {
> $ui_diff insert end [append \
> "* " \
> [mc "Git Repository (subproject)"] \
>- "\n"] d_@
>+ "\n"] d_info
> } elseif {![catch {set type [exec file $path]}]} {
> set n [string length $path]
> if {[string equal -length $n $path $type]} {
> set type [string range $type $n end]
> regsub {^:?\s*} $type {} type
> }
>- $ui_diff insert end "* $type\n" d_@
>+ $ui_diff insert end "* $type\n" d_info
> }
> if {[string first "\0" $content] != -1} {
> $ui_diff insert end \
> [mc "* Binary file (not showing content)."] \
>- d_@
>+ d_info
> } else {
> if {$sz > $max_sz} {
> $ui_diff insert end [mc \
> "* Untracked file is %d bytes.
> * Showing only first %d bytes.
>-" $sz $max_sz] d_@
>+" $sz $max_sz] d_info
> }
> $ui_diff insert end $content
> if {$sz > $max_sz} {
> $ui_diff insert end [mc "
> * Untracked file clipped here by %s.
> * To see the entire file, use an external editor.
>-" [appname]] d_@
>+" [appname]] d_info
> }
> }
> $ui_diff conf -state disabled
>@@ -442,10 +442,10 @@ proc read_diff {fd conflict_size cont_info} {
> } elseif {$is_submodule_diff} {
> if {$line == ""} continue
> if {[regexp {^Submodule } $line]} {
>- set tags d_@
>+ set tags d_info
> } elseif {[regexp {^\* } $line]} {
> set line [string replace $line 0 1 {Submodule }]
>- set tags d_@
>+ set tags d_info
> } else {
> set op [string range $line 0 2]
> switch -- $op {
Looks great. Thank you.
--
Pat Thoyts http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD
prev parent reply other threads:[~2010-12-06 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 11:41 [PATCH] Fix use of hunk tag for non-hunk content Bert Wesarg
2010-12-06 21:25 ` Pat Thoyts [this message]
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=87ei9uy4o8.fsf@fox.patthoyts.tk \
--to=patthoyts@users.sourceforge.net \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
/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