Open Ulibos opened 1 month ago
PR welcome!
See also:
A
Oh well, github search really struggles with finding flags (or maybe it's just a skill issue). I did honestly try to search for similar issues to avoid spawning duplicates but here we are.
I will try to come up with a PR but english is not my forte and I will most likely need a helping hand on making it sound ok.
Addressed in this PR: #12685
The issue
As many people (me included) tend to familiarize themselves with tools by extending examples, this particular flag is a big issue. It is the first ever flag one will see when they open up a
Makefile
ormake.bat
. Yet it's documentation is minimal and is hidden far away from a place a novice would reach out for in the first place. I literally had to search through github for the flag to find it mentioned in docs and find it's docs page by an excerpt from a nearby paragraph (because using the flag name directly in search engines does not help).Why it's a problem
The fact that
-M
requires a very strict order of arguments and modifies provided paths is not apparent, yet it conflicts with the rest or the cli tool signature. It causes one to get unexpected export paths and there is no mention of it in the--help
output which makes one to spend a lot of time debugging the issue.Fix suggestion
--help
output should display both call signatures and have at least a paragraph explaining what-M
is intended for and how it affects args ordering:I would even go as far as suggesting also adding at least a note to a Getting Started page for people to know that that example is NOT the default signature and maybe even mention it in make files themselves.