LucasLarson/dotfiles

add function-scope preference for unescaped pathnames

LucasLarson opened this issue · 0 comments

LucasLarson commented

show unescaped pathnames where git is already serving human-friendly content

  • add -c quotePath=false where git command to target audience-human output instead of git status where scripting is not possible or likely

Where git config allows for scope-wide preference for escaping “unusual[ly]”1 named paths,2 the same functionality is available on a per-invocation level,3 which allows for temporary syntactic sugar without blindingly blunted defaults (the default behavior is to escape and quote such content, which is the safest and most reasonable default, especially in situations where a machine or other third party might parse the output).

To that end, in the instances where this repository calls for a function-scope -c color.status=always, it should call also for unescaped pathnames -c core.quotePath=false.

Footnotes

  1. scare quotes in original4 ↩

  2. git config core.quotePath=false ↩

  3. git -c core.quotePath=false status, for example, instead of git status ↩

  4. https://github.com/git/git/commit/9378c16135 ↩