-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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? Sign in to your account
Ignore URIs #34
Comments
oh. I see from that #20 that this feature request may have been overly optimistic:
Perhaps Spelunker should parse the texts. If Spelunker doesn't parse the current buffer in some way, how exactly does it handle CamelCase, snake_case, acronyms, and so on? Is there really no way for Spelunker to at least post-process the results of whatever is parsing the current buffer to filter out false positives like URIs and `-delimited substrings? Spelunker is such a dramatic improvement over the default spell checker. It'd be the shame of 2020 if this is ultimately infeasible due to "reasons." 😭 If Spelunker itself can't filter out false positives, is there at least a way for end users themselves to do so (e.g., by manually adding some kind of |
Hi, @leycec!
And now, you can use these options. |
It'd be swell if Spelunker were URI-aware. Currently, both [Neo]Vim's default spell checker and Spelunker incorrectly spell check words embedded within URIs. While we can't do much about [Neo]Vim, Spelunker should ideally auto-whitelist (i.e., not spell check) anything matching a URI.
Under the default spell checker, doing so is mostly trivially. For example, this well-documented one-liner excludes all URIs in Python comments and strings from spell checking when added to
~/.vim/after/syntax/python.vim
:Of course... Spelunker ignores that entirely. URI substrings are yet again highlighted as spelling mistakes, much to the consternation of the spelling Nazi inside all of us. Cue sad panda.
It'd be a spelling miracle on Earth if Spelunker instead either:
Thanks for all the generous volunteerism over the years, @kamykn. Let's keep on spelunkin'!
The text was updated successfully, but these errors were encountered: