mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup and wontfix this

Browse source
This commit is contained in:
Joey Hess 2023-11-21 16:11:10 -04:00
parent 96c269e087
commit e08f170b0e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 24 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/fsck_ignores_--json-error-messages_when_--quiet.mdwn
View file

@ -73,4 +73,4 @@ fsck: 1 failed
Yes, great tool ! Thanks !
> [[wontfix|done]] per my comment --[[Joey]]

23
doc/bugs/fsck_ignores_--json-error-messages_when_--quiet/comment_1_a23d96af8c0e418350a73cbce5bc24be._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-11-21T20:03:45Z"
content="""
Hmm, I've never considered combining --quiet with --json. It's kind of
undefined and really not clear to me what it should do.
But, --json-error-messages makes the json contain an error-messages field,
and the error message is in there. So you can just extract that and ignore
the other messages in the json output. No need to use --quiet then.
I suppose there may be someone who uses --json as a matter of course, but
adds --quiet to that when they want to disable the json output. So
changing the current behavior, ill-defined as it is, would be asking for
trouble.
What actually happens currently is which ever output option comes last
overrides earlier options. So `--json --quiet` is quiet, and `--quiet
--json` outputs json. `--json-error-messages` is like `--json` in this
regard to. Which is just behavior that fell out of the option parser
implementation.
"""]]