| T O P I C R E V I E W |
| pbrown |
Posted - Dec 05 2009 : 1:26:32 PM
VAX has a spell checker for comments and strings in source code which I find fairly useful.
In addition to coding, I frequently find myself editing a collection of documents that are in plain text. I currently edit these files with the Emacs text editor, but am interested in using Visual Studio to edit them instead to take advantage of project features (including VAX's very fast "open file in project" dialog).
Spell checking in these files would be very useful. Is there a way to enable spell checking on the entire body of a text file? If not, would this be an easy feature to add? |
| 8 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Jan 31 2010 : 1:38:12 PM
case=36834 is fixed in build 1810 |
| accord |
Posted - Dec 12 2009 : 5:22:01 PM
I have put in a bug report for this:
case=36834 |
| pbrown |
Posted - Dec 10 2009 : 4:13:14 PM
Yes, I can reproduce your results where spell checking does work after switching to/from a .cpp file. Thanks. |
| accord |
Posted - Dec 09 2009 : 3:23:16 PM
I was playing a little with this and found that spell check on .txt files are grayed out when I re-open the project that contains my new .txt file. But after I switch to a file where spell checker works (f.e. a cpp file) than back to the .txt file, spell checking remains active. Can you confirm this?
About underlines: case=560 is the case for it. |
| pbrown |
Posted - Dec 07 2009 : 5:35:27 PM
accord, I am able to reproduce your findings on VS2008 SP1 and VAX 1738. If I create a new project and add an existing '.txt' file to it, the manual spell check under VAssistX->Tools works. However, if I close Visual Studio and then reopen the same project, Spell Check is now disabled when I am editing the same text file.
In my original repro, where it was already grayed out, I had already created a project and added a zillion text files to it. Two other things special about that case in case it matters:
(1) The project itself was created outside VS2008 using a Perl script I wrote that directly generates XML.
(2) The text files in the project are read-only. I am using Perforce for source code control, and Perforce makes all files read-only if they are not checked out for edit.
In any event, this isn't that important to me -- the underline-style spell checking is what I was really asking for. :-)
Thanks,
Pat |
| accord |
Posted - Dec 07 2009 : 12:48:52 PM
Yes, I meant VAssistX -> Tools -> Spell Check.
What version of Visual Studio and Visual Assist do you use?
I started Visual Studio 2008 SP1, created a new txt file using
File -> New -> File... -> General -> Text file
typed some text into it, then run Spell Check and it worked. I'm using VAX 1738.
Do you see the same effect if you do these steps? |
| pbrown |
Posted - Dec 06 2009 : 1:59:43 PM
I assume "if you ask VA to do it" means the manual spell check option (VAssistX -> Tools -> Spell Check)? If so, that doesn't work on my system -- the option is disabled (grayed out) when the current document is a .TXT file.
|
| accord |
Posted - Dec 06 2009 : 09:31:54 AM
You can spell check in txt files if you ask VA to do it. We are planning to enable underlining as well:
case=560 |
