init: Avoid autoenabling special remotes that have control characters in their names
authorJoey Hess <joeyh@joeyh.name>
Wed, 12 Apr 2023 16:33:17 +0000 (12:33 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 12 Apr 2023 16:37:12 +0000 (12:37 -0400)
commitc50aa21d5f1468fb54d5e8d65455446897443054
treedddccd3fa309a76f702e1d513decc6729b416497
parentde68e3dd4f427c834b6d0472853f34772cad425b
init: Avoid autoenabling special remotes that have control characters in their names

I'm on the fence about this. Notice that pulling from a git remote can
pull branches that have escape sequences in their names. Git will
display those as-is. Arguably git should try harder to avoid that.

But, names of remotes are usually up to the local user, and autoenable
changes that, and so it makes sense that git chooses to display control
characters in names of remotes, and so autoenable needs to guard against
it.

Sponsored-by: Graham Spencer on Patreon
Annex/SpecialRemote.hs
CHANGELOG
doc/todo/terminal_escapes_in_filenames.mdwn