improve match explanations
authorJoey Hess <joeyh@joeyh.name>
Wed, 26 Jul 2023 19:29:23 +0000 (15:29 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 26 Jul 2023 19:37:03 +0000 (15:37 -0400)
commit499d01412308da0cf031946e9d46fd9439f41add
tree68c468bc936a348900a58a1d8c2bf9944ebb6055
parent08071a1b90060c93acf07f79535ee92d3bf24168
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
Limit.hs
Messages.hs
doc/git-annex-common-options.mdwn
doc/todo/option_to_explain/comment_2_71616074104ab70eb76ad5edb9207b5c._comment [new file with mode: 0644]