From: mark <markkicks@gmail.com>
To: "Jacob Helwig" <jacob.helwig@gmail.com>
Cc: git@vger.kernel.org, kde@mail.kde.org
Subject: Re: git log, outputs something weird for colors
Date: Mon, 12 Jan 2009 14:33:14 -0800 [thread overview]
Message-ID: <82fa9e310901121433p67f7bb3ai330439bf3c00df26@mail.gmail.com> (raw)
In-Reply-To: <8c9a060901121428j37ff6699g7af264f79829b6de@mail.gmail.com>
On Mon, Jan 12, 2009 at 2:28 PM, Jacob Helwig <jacob.helwig@gmail.com> wrote:
> On Mon, Jan 12, 2009 at 13:51, mark <markkicks@gmail.com> wrote:
>> hi
>> i am using kde konsole, and i am getting weird output for colors, for
>> example for git log i get the following output
>>
>>
>> git log
>> ESC[33mcommit 8b918256d944221f741e5d7300873810e31466a6ESC[m
>>
>>
>> settings in my bash and git.
>>
>> export | grep -i term
>> declare -x TERM="xterm-256color"
>>
>>
>> ~/.gitconfig
>> [color]
>> branch = auto
>> diff = auto
>> status = auto
>>
>> do you know what is wrong?
>> thanks
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> I don't have any problems with Konsole and git's coloring, but my TERM
> is set to "xterm", not "xterm-256color".
even xterm does not work for me!
but git status, and git branch give the correct color. the problem is
only with git log!
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
next prev parent reply other threads:[~2009-01-12 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 21:51 git log, outputs something weird for colors mark
2009-01-12 22:28 ` Jacob Helwig
2009-01-12 22:33 ` mark [this message]
2009-01-12 22:38 ` mark
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=82fa9e310901121433p67f7bb3ai330439bf3c00df26@mail.gmail.com \
--to=markkicks@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacob.helwig@gmail.com \
--cc=kde@mail.kde.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;
as well as URLs for NNTP newsgroup(s).