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

Re: inconsistent logs when displayed on screen / piped to a file

From
MMMojca Miklavec <mojca.miklavec.lists@gmail.com>
Date
Jul 30, 2012, 14:58 UTC
Message-ID
<CALBOmsage+Gx9=bkH0rX1SvViSbMUPUWuYoifjgEnsjw+0=osw@mail.gmail.com>
In-Reply-To
<50168E93.2090202@drmicha.warpmail.net>
On Mon, Jul 30, 2012 at 3:39 PM, Michael J Gruber wrote:
Show 20 quoted lines
> Mojca Miklavec venit, vidit, dixit 30.07.2012 14:25:
>>
>> I'm trying to use "git log" to generate ChangeLog for a project
>> recently migrated from CVS.
>>
>> The problem is that
>>     git log --summary --stat --no-merges --date=short --decorate=short
>> behaves differently when the result is displayed on screen and when it
>> is piped to a file.
>
> The only difference that I see is the formatting. ("..." is merely an
> abbreviation for a leading path.)
>
> a) probes your terminal for the number of columns and uses all available
> space.
>
> b) goes to a file and has no connected terminal, thus uses a default
> column number. You can change that number using
>
> COLUMNS=YourNumber git log YourArgs > YourFile

Wow, perfect, thank you very much. Setting COLUMNS=200 (the high number just in case) solved the problem.

Mojca
Previous: Carlos Martín NietoNext: Jan Engelhardt
Message 4 of 5 in “inconsistent logs when displayed on screen / piped to a file”
  1. Mojca MiklavecJul 30, 2012
  2. Michael J GruberJul 30, 2012
  3. Carlos Martín NietoJul 30, 2012
  4. Mojca MiklavecJul 30, 2012
  5. Jan EngelhardtJul 31, 2012

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.