git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [kde] kde konsole color settings in terminal

From
Boyd Stephen Smith Jr. <bss@iguanasuicide.net>
Date
Jan 12, 2009, 22:18 UTC
Message-ID
<200901121618.52636.bss@iguanasuicide.net>
In-Reply-To
<82fa9e310901121335p4bd1e223x8eea1881c0add364@mail.gmail.com>
On Monday 2009 January 12 15:35:08 mark wrote:
Show 5 quoted lines
>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

Looks like konsole isn't interpreting the color codes. However, it also looks like git doesn't use termcap/terminfo/etc. to determine the correct way to write colors for your terminal and just defaults to ANSI.

Do you get odd output from: grep --color=always o <<< foo or are the "o"s properly colored red?

>settings in my bash and git.
>
>export | grep -i term
>declare -x TERM="xterm-256color"

So you have a /usr/share/terminfo/k/konsole-256color file? If so, it might be better to use TERM="konsole-256color".

I never use 256 color mode, so I'm not clear on how that works. However, what git is outputting look more like ANSI 16-color codes.

Does this work as you expect in other terminal applications (like rxvt or xterm or gnome-terminal) with the same settings for TERM?

Just to let you know, it works here (openSUSE 11.1) with Konsole 1.6.6 (KDE 3.5.10) running git 1.6.0.2 inside screen 4.00.02

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss@iguanasuicide.net                     ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.net/                      \_/     
Next: mark
Message 1 of 2 in “Re: [kde] kde konsole color settings in terminal”
  1. Boyd Stephen Smith Jr.Jan 12, 2009
  2. markJan 12, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.