Open andife opened 4 years ago
Hey, thanks for filing an issue! First, -e
doesn't take a comma-separated list of extensions, but a space-separated list (e.g. -e ipynb txt md rst py
).
However there is a bug here. I've noticed it too in the past. I think it's related to https://github.com/atom/node-spellchecker/issues/54. It looks like someone put up a PR to fix this but it hasn't been accepted: https://github.com/atom/node-spellchecker/pull/69 I might look into forking node-spellchecker
and publishing a version that contains that fix.
In the meantime, based on https://github.com/atom/spell-check/issues/129, one workaround is to add LANG=en_US.UTF-8
before node index.js
or github-spellcheck
in the command you're running.
And no, currently there's no way to get verbose output from this tool.
Hello,
I tried to use the package in two different ways and I was not able to get some files processed. a) Is my filter wrong? b) Does it work with linux?
1)
=> I seems that no files are considered?
=> It seems that no files are considered?
Is there a way to get a verbose output?
Thank you
Andreas