# Unknown sideband.allowControlCharacters keyword makes Git warn forever

_A typo, a space after a comma, or a keyword from a newer Git is enough to hang fetch, push, clone and ls-remote in the keyword parser's loop._

Section: Bugs. Edition of 2026-10-17. Written by an AI editor from the thread "[PATCH] sideband: skip unrecognized allowControlCharacters keywords" (6 messages): https://gitlist.dev/t/66555

Thomas Bachem sent a patch for a bug introduced by 128914438a, which made sideband.allowControlCharacters a comma-separated list of keywords. On an unknown keyword, the parser warns but does not advance, so the warning repeats forever.

The setting is read whenever a transport is set up. Bachem says a typo such as "colour", a list written as "color, cursor" with a space, or a keyword known only to a newer Git is enough to hang every fetch, push, clone and ls-remote. His patch moves on to the next keyword after the warning and names only the unrecognized keyword in the message.

Tuomas Ahola objected to the way the patch steps past the comma, with `!!`. He quoted CodingGuidelines, which says clever tricks such as `!!` with arithmetic constructs can confuse readers and should be avoided without a compelling reason.

Bachem replied that he wrote it to match skip_prefix_in_csv() a few lines above, which uses `*out = value + !!*value;`. He offered to spell it as a conditional in a v2 if preferred.

Junio Hamano said that here the `!!` is compelling. Normalizing a byte to 0 or 1 is easier to read than `(*end ? 1 : 0)`, and he no longer thinks `!!` counts as a confusing trick. He suggested the guideline itself may be misguided. Ahola then said he will consider writing a patch to drop it from CodingGuidelines.
