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

Re: [PATCH 2/2] gitk: add text wrapping preferences

From
Johannes Sixt <j6t@kdbg.org>
Date
Dec 12, 2024, 18:58 UTC
Message-ID
<c6cc8704-6043-4e6d-bc4a-d9801a372710@kdbg.org>
In-Reply-To
<e116685568e4f1db3bc71985945f0ff4e40e12fc.1733767737.git.gitgitgadget@gmail.com>
Am 09.12.24 um 19:08 schrieb Christoph Sommer via GitGitGadget:
Show 7 quoted lines
> From: Christoph Sommer <sommer@cms-labs.org>
> 
> Add a new preference "wrapdefault" which allows enabling char/word wrap.
> Impacts all text in the ctext widget for which no other preference exists.
> 
> Also make the (existing) preference "wrapcomment" configurable graphically.
> Its setting impacts only the "comment" part of the ctext widget.

Nice! I agree that it makes sense to wrap the comment differently than the patch text section. I notice, though, that the patch text wrapping is also applied to the commit header section. Personally, I don't mind it. If someone needs a third option, they can take this patch as a blueprint.

-- Hannes
Previous: Christoph Sommer via GitGitGadget
Message 5 of 5 in “gitk: text wrapping in ctext (commit headers, subject, and body)”
  1. 0/2 gitk: text wrapping in ctext (commit headers, subject, and body)Christoph Sommer via GitGitGadget, Dec 9, 2024
  2. 1/2 gitk: make headings of preferences boldChristoph Sommer via GitGitGadget, Dec 9, 2024
  3. Johannes SixtDec 12, 2024
  4. 2/2 gitk: add text wrapping preferencesChristoph Sommer via GitGitGadget, Dec 9, 2024
  5. Johannes SixtDec 12, 2024

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.