-
Notifications
You must be signed in to change notification settings - Fork 26
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
VSCode support for bad chars #225
Comments
@lonix1 good catch,thanks! 👍 I guess this extension can still be useful, at least with some characters VSCode doesn't plan to highlight. We have to define which characters should be removed from the extension. |
You're right - it would be good not to redo the work vscode already does, and handle only bad chars that vscode doesn't catch. But how would we even know how to detect that? They say
So it's not clear which chars they target. |
I am also interested in this |
There are some characters that this extension highlights by default that VSCode does not ( As far as features that this extension provides that VSCode does not, I can think of the following:
Also, "Zap Gremlins" was on the roadmap, allowing for quick removal of special characters. |
@TheSench Thank you for the detailed overview. In fact in might be a good idea to add that list to the docs, because I'm sure many users will wonder about this now. |
I want to use this extension to highlight certain characters I care about. Such as the letter "A", in certain situations where it isn't commonly invalid, just in the files / file formats I care about. |
I just spent a lot of time trying to figure out, why one worked and the other didn't, just to find the old "en-dash vs hyphen" to be the gremlin. nmap -p 139,445 -Pn -script smb-enum* 127.0.0.1 nmap -p 139,445 -Pn –script smb-enum* 127.0.0.1 It didn't blow up, it just didn't work 😫 True, the |
VSCode now has built-in support for detecting "bad" characters.
Is this extension obsolete, or does it offer more features? I've been using it for a while and unsure whether to keep it or not?
The text was updated successfully, but these errors were encountered: