Comment author: @shindere

As such I find this issue a bit vague. Would it be possible to add issues for each such inconsistency? Such more precise issues would be easier to work on and close.

Comment author: @gasche

Yes, the idea is to open issues for each such inconsistency, but to mark them all as children of this meta-issue (an issue about issues), so that it is easy to navigate from one to another of these issues -- this issue effectively collects a list, as well as giving us a central place in which to have discussions about command-line mismatches in general.

(You may ask what's the difference between meta-issues and tags. I have a personal tendency to use meta-issues to group related bugs together, and tags to describe a cross-cutting methodology aspect of an issue, but I'm not sure this distinction is always consistently done.)

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

This meta-issue has been silent so I will close it now.

It can always be reopened if it becomes useful again in the future.