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

Re: Recoding of {git,cg}-log output

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 27, 2006, 00:36 UTC
Message-ID
<Pine.LNX.4.63.0602270133330.5275@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<44024384.4060406@people.pl>
Hi,
On Mon, 27 Feb 2006, Krzysiek Pawlik wrote:
> First: a little "why": having /usr/bin/vim as PAGER allows to enter
> UTF-8 commit messages quite easily, the problem is when git-log (or
> cg-log) is run in terminal that's not UTF-8.

Of course, you could always set up a script doing the recoding and the paging, like

-- snip -- #!/bin/sh

iconv -f UTF-8 -t ISO-8859-2 "$@" | vim -- snap --

and point your PAGER to that script (which is untested BTW). The advantage of this approach compared to adjusting git is that other programs use PAGER, too.

Hth, Dscho

Previous: Krzysiek PawlikNext: Krzysiek Pawlik
Message 2 of 4 in “Recoding of {git,cg}-log output”
  1. Krzysiek PawlikFeb 27, 2006
  2. Johannes SchindelinFeb 27, 2006
  3. Krzysiek PawlikFeb 27, 2006
  4. Petr BaudisFeb 27, 2006

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.