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

Re: conflict markers in markdown files

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 29, 2021, 05:08 UTC
Message-ID
<xmqq5ytgo1u2.fsf@gitster.g>
In-Reply-To
<00c601d7cc53$0ce58800$26b09800$@nexbridge.com>
<rsbecker@nexbridge.com> writes:
Show 7 quoted lines
> It sounds like we might need an attribute like:
>
> *.md	conflict-marker-size=32,conflict-marker-separator='~'
>
> to stick 32 ~ characters as a separator, if going down that path. I'm not
> sure how hard this would be, but tooling other systems, like JGit and every
> client on the planet would be painful.

Well, the underline-style markdown headers can use tilde for headers below the level that uses hyphens, so you'd need to pick a different separator letter ;-). I agree that third-party application would have trouble with an arbitrary setting of the marker appearance (note that our own "rerere" knows about the attribute).

Previous: rsbecker@nexbridge.com
Message 9 of 9 in “conflict markers in markdown files”
  1. Nicholas Bransby-WilliamsOct 28, 2021
  2. Philip OakleyOct 28, 2021
  3. Junio C HamanoOct 28, 2021
  4. Nicholas Bransby-WilliamsOct 28, 2021
  5. Junio C HamanoOct 28, 2021
  6. Nicholas Bransby-WilliamsOct 28, 2021
  7. Junio C HamanoOct 28, 2021
  8. rsbecker@nexbridge.comOct 28, 2021
  9. Junio C HamanoOct 29, 2021

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.