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

Re: General output formatting

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 27, 2025, 18:40 UTC
Message-ID
<xmqqfrjz6xkc.fsf@gitster.g>
In-Reply-To
<18ed50b3-e5a4-43b3-a543-f9a3d2c309e6@xiplink.com>
Marc Branchaud <marcnarc@xiplink.com> writes:
> I have no opinion on exactly how to "butcher" the output for a
> terminal.   I guess it depends on how well Git wants to support
> copy/paste of its output.
Yup, that is a fine balancing act.  Given the current behaviour,
    $ cat .git/config
    [core]
            somevalue = "true\b\b\b\bfalse"
    $ git config --local --list
    core.somevalue=false
supporting copy-paste may not be such a good thing to do, though ;-)
Previous: Marc BranchaudNext: Phillip Wood
Message 14 of 15 in “\b character escapes in CLI usage”
  1. Yaakov SmithFeb 25, 2025
  2. Jeff KingFeb 26, 2025
  3. Jeff KingFeb 26, 2025
  4. Junio C HamanoFeb 26, 2025
  5. Kyle LippincottFeb 26, 2025
  6. Jeff KingFeb 26, 2025
  7. Junio C HamanoFeb 26, 2025
  8. brian m. carlsonFeb 26, 2025
  9. Junio C HamanoFeb 26, 2025
  10. Junio C HamanoFeb 27, 2025
  11. General output formatting (was: Re: \b character escapes in CLI usage)Marc Branchaud, Feb 27, 2025
  12. Junio C HamanoFeb 27, 2025
  13. Marc BranchaudFeb 27, 2025
  14. Junio C HamanoFeb 27, 2025
  15. Phillip WoodFeb 27, 2025

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.