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

Re: CR codes from git commands

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2009, 16:59 UTC
Message-ID
<7v63k6x8j7.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<18809.60512.654436.59819@hungover.brentg.com>
Brent Goodrick <bgoodr@gmail.com> writes:
Show 5 quoted lines
>  - Bare minimum: Add a new --no-cr option (e.g., "git --no-cr
>    ...
>  - Nice-to-have: Add a "git --no-progress" message that would never
>  ...
> Both options are intended to be independent of each other.
I do not think so.  --no-progress should imply --no-cr ;-)

I do not think it makes much sense to pollute your non-terminal with 100 lines of 1%,2%,3%,...100% if it cannot sensibly do carriage-returns. It may be another knob to tweak, but it's a kind of thing you implement because you could, not because it makes sense. I would be mildly against no-cr.

I suspect we may even be able to solve it without adding --no-progress. Perhaps some commands do not have --quiet to squelch progress and teaching them --quiet will solve the issue for you?

Previous: Brent GoodrickNext: Johannes Schindelin
Message 14 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.