Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to replace with a dash involved

See original GitHub issue

This command fails:

renamer --find '_Small' --replace '-sm'

because it thinks -sm is another command line flag that it doesn’t recognize. I assume this is actually an issue with what library you’re using for argument parsing, but I thought you would want to know, as there are plenty of other argument parsers to choose from. Here’s the output:

As you can see, it confuses the program a bit.

Issue Analytics

State:
Created 8 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

75lbcommented, Dec 3, 2016

Fixed and released in renamer v0.6.1.

The “Unable to replace with a dash involved” issue is resolved within the command-line-args module, which renamer uses.

See here for a description how to avoid ambiguous values. In summary, you use --option=value notation, for example:

renamer --find '_Small' --replace='-sm'

0reactions

ismyrnowcommented, Apr 8, 2016

I get similar output for the guide using the standard command prompt on Windows 7, and node 0.10 (not my typical environment, but possibly worth mentioning). The font there is “Terminal”.