Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
This is a minor issue, but potentially confusing for novices. I'd suggest that "Usage:" should say "markdownlint" instead of "cli":
Usage: cli [options] <files>
MarkdownLint Command Line Interface
-h, --help output usage information
-V, --version output the version number
-c, --config [configFile] Configuration file
As an extremely minor point, the 'O's of "Output" might be capitalized and the 'V' of "-V" lower-cased for consistency with the other switches.
The text was updated successfully, but these errors were encountered:
It is interesting, I see it as correctly:
Have you installed it globally (-g)? As far as I see you are using Windows.
Sorry, something went wrong.
Commander attempts to infer the tool name if it is not passed in - see Command.prototype.parse.
On Windows (including when installed globally), argv at that point looks like:
[ 'C:\\Program Files\\nodejs\\node.exe',
Therefore, commander infers the name "cli".
One fix might be to rename cli.js to markdown.js. Another might be something like the following:
var pkg = require('./package');
var commander = require('commander');
var program = new commander.Command(pkg.name.replace(/-.*$/, ''));
If you like, I can send a pull request - or feel free to make the change yourself if you like it.
For now I just renamed it.
But I don't like it already, if i will see more issues like this, i will rewrite it using meow, argparse, minimist anything like that instead of commander.
No branches or pull requests