subject="""comment 1"""
date="2020-01-22T15:11:05Z"
content="""
-I've said this before, but I'll say it one more time: --json-error-messages
-is not a guarantee that every possible error message that may be output by
-git-annex in some exceptional circumstance will be formatted as json.
-
-In this case, while I happened to make it be captured in an unrelated
-change, there's actually no benefit to it being captured. If it were no
-longer captured tomorrow, I would not consider that a bug. This error
-message is not specific to a particular file in the repository, so if
+This error message is not specific to a particular file in the repository, so if
git-annex get outputs it, it doesn't help for the error message to be
wrapped up in json. The actual purpose of --json-error messages is being
able to correlate a failure to eg, get a particular file with an error
message related to that action. Not in avoiding all possible stderr.
-----
-
-The extra newlines output to stdout are there because the `warning` action
-does not know if something may have been output to stdout earlier without a
-terminating newline, and it wants to avoid an ugly interleave of stdout and
-stderr. While state could be maintained to keep track of that, the end
-result would be git-annex would become some milliseconds slower, and it
-does not seem worth the complexity or minor speed hit to cater to the case
-where stderr is /dev/nulled. Note that this doesn't happen when using
---json. Also, IIRC it's avoided when using concurrent output, which does
-pay the time/complexity overhead already to keep track of the state of the
-display to that extent. Anyway, I'm obviosuly not going to leave this bug
-report open for such a minor and tangential issue after the main issue in
-it is fixed, so it's kind of annoying to need to write this wall of text
-about it. May I suggest one bug report per distinct issue is a good way to
-avoid my current annoyed state?
+The actual bug here is that it dumps git config to stderr at all.
----
-Not wanting to sit down and write all this is why, the previous two or
-three times I opened this issue, I promptly closed the window rather than
-addressing any part of it.
+The extra newlines are output to stdout, so not a problem WRT stderr.
"""]]