Analyzer disabling discussion continued #298
Replies: 6 comments 2 replies
-
The code analyzer only spell checks the identifiers in the code. It doesn't spell check anything else. Comments and strings are still handled by the tagger. I did not move spell checking of those elements over to the analyzer due to its limitations with adding words to the dictionaries and ignored words files. By disabling the code analyzer, it effectively works as it has done in the past. |
Beta Was this translation helpful? Give feedback.
-
I think I explained it poorly. I'm wondering if I can get the code to behave the same as comments.
I'd like to do the "spell check solution" menupic, and have that dialog show both comments and code. No analyzers at all 🙂
I appreciate the response btw. This spell checker blows away any other one I've tried, even paid ones. It's quality.
…________________________________
From: Eric Woodruff ***@***.***>
Sent: Friday, July 28, 2023 1:04:02 PM
To: EWSoftware/VSSpellChecker ***@***.***>
Cc: Greg Robertson ***@***.***>; Author ***@***.***>
Subject: Re: [EWSoftware/VSSpellChecker] Analyzer disabling discussion continued (Discussion #298)
[External Sender]
The code analyzer only spell checks the identifiers in the code. It doesn't spell check anything else. Comments and strings are still handled by the tagger. I did not move spell checking of those elements over to the analyzer due to its limitations with adding words to the dictionaries and ignored words files. By disabling the code analyzer, it effectively works as it has done in the past.
—
Reply to this email directly, view it on GitHub<#298 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANJZCGLV33LGQGLDJT4FOJDXSPWIFANCNFSM6AAAAAA23XDQCY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Solution/project spell check is implemented purely in code that I wrote and doesn't involve any of the Visual Studio APIs. It uses a series of regular expressions to extract things that look like strings and comments from the files in the project classifying them by extension. Implementing support for identifiers based on the language would be too difficult since you would have to parse the actual code in some way based on the language. I'm not sure of a good way to accomplish that. |
Beta Was this translation helpful? Give feedback.
-
You could but I think you'd have way too many false positives to have it be of any use since it won't apply any of the C# options that control how it spell checks the comments and strings under normal circumstances. There are instructions in the referenced topic for replacing a handler with one of your own in the user configuration file so you could give it a try. You'd just add an entry to remap the "cs" extension to the "PlainText" classifier. |
Beta Was this translation helpful? Give feedback.
-
Sorry if this is off topic but it seems related. I've been trying to figure out how to configure I can create an issue for the bad configuration behavior but I may not be able to produce any logs for it. |
Beta Was this translation helpful? Give feedback.
-
You can also set it to silent or none which gets rid of all the markers but that's effectively turning it off so you might as well use the spelling configuration option. |
Beta Was this translation helpful? Give feedback.
-
Hi, sorry to be a thorn in your side, thought I could start a discussion here instead of in the issues. I'm attempting to disable the C# code analyzer, so I can have it spellcheck C# code the same way it does comments for now. Based on the feedback, I disabled the analysis checkbox in general settings.
However, at that point, the code analysis was disabled, except it also wasn't spellchecking the code (the comments where still getting checked). There's something here I'm missing.
Beta Was this translation helpful? Give feedback.
All reactions