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

Re: CR codes from git commands

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 20, 2009, 17:08 UTC
Message-ID
<alpine.DEB.1.00.0901201757520.5159@intel-tinevez-2-302>
In-Reply-To
<18805.64312.289059.660023@hungover.brentg.com>
Hi,
On Tue, 20 Jan 2009, Brent Goodrick wrote:
> I am considering converting from CVS over to using git. I'm currently
> using git version 1.5.6.5 on Debian Linux "testing".

First of all, 1.5.6.5 is from last August, so chances are that the behavior you complain about was fixed in the meantime. We're at 1.6.1 at the moment.

Show 6 quoted lines
> One of the first things I ran into was having to set PAGER to "cat" to 
> avoid the problems when running git from anything other than a terminal.  
> The second thing is that "git pull" (and possibly other commands) are 
> emitting ^M (octal 013) codes on output, possibly caused by the same 
> assumption as causes the problem that is fixed by setting PAGER to 
> "cat".

The only place I can think about where a CR is output is when showing the progress of downloading. 

Usually, our code checks if stdout is a tty, and does not show progress.
As a work-around, piping into cat should work, though.

Ciao, Dscho

Previous: Brent GoodrickNext: Daniel Barkalow
Message 2 of 24 in “CR codes from git commands”
  1. Brent GoodrickJan 20, 2009
  2. Johannes SchindelinJan 20, 2009
  3. Daniel BarkalowJan 22, 2009
  4. Brent GoodrickJan 22, 2009
  5. Daniel BarkalowJan 22, 2009
  6. Junio C HamanoJan 22, 2009
  7. Mike RalphsonJan 22, 2009
  8. Brent GoodrickJan 22, 2009
  9. Mike RalphsonJan 22, 2009
  10. Johannes SchindelinJan 22, 2009
  11. Daniel BarkalowJan 22, 2009
  12. Johannes SchindelinJan 22, 2009
  13. Brent GoodrickJan 23, 2009
  14. Junio C HamanoJan 23, 2009
  15. Johannes SchindelinJan 23, 2009
  16. Brent GoodrickJan 24, 2009
  17. Johannes SchindelinJan 24, 2009
  18. Boyd Stephen Smith Jr.Jan 25, 2009
  19. Brent GoodrickJan 25, 2009
  20. Brent GoodrickFeb 2, 2009
  21. The lifecycle of a patch and the maintainer involvementJunio C Hamano, Jan 25, 2009
  22. Brent GoodrickJan 21, 2009
  23. Johannes SchindelinJan 21, 2009
  24. Brent GoodrickJan 22, 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.