git-annex/doc/todo/option_to_explain
Joey Hess 499d014123
improve match explanations
Using == and != proved too hard to read, so went with [TRUE] and [FALSE]
after the term. I would kind of liked to have used emojis for a green
check and red X, but probably that is too fancy to be a good idea.

Make --explain output be inside [ ] with whitespace around them, to
avoid it ending with eg "[FALSE]]" and to make it easier to visually
find the start of it.

Sponsored-by: Dartmouth College's DANDI project
2023-07-26 15:37:03 -04:00
..
comment_1_81644886e14851a276dc3c89965df62e._comment
comment_2_71616074104ab70eb76ad5edb9207b5c._comment