Community
Participate
Working Groups
I20070606-0010 I would like to be able to select a set of resources and have an action like: 'Find spelling Errors' A view should show all errors found (could be the search view, could be a separate view). The view should allow to goto the spelling error and add words to the user dict. Reason: I'm spell checking the help at the moment, which means I have to open each file in an editor, which is pain full. Hint: I know eclipse is not an office suite, but I think this is a low hanging fruit.
*** Bug 275532 has been marked as a duplicate of this bug. ***
Created attachment 139425 [details] Proposed fix This patch implements the request. A search page is added allowing to: - Choose the file name pattern of the files to check - Choose the search scope (selection, workspace, working set, enclosing project) - Choose the spelling engine (if more then one is available) A search result page shows the result. The page has the same features as the text search result view, including colored labels, and tree/table view. In addition actions are provided to: - Fix spelling problems This is product quality code, but, to be able to provide such a small patch with such a rich feature set it is required to reuse tons of code from the text file search. Most of this code is internal, and hence, the spelling search must live in the org.eclipse.search plugin, if we don't want to provide additional API (which I guess we don't). Things to do: - Search page should remember last selections - Spelling Problem Search icon - Tests?
Dani, I don't know if platform/text resp. platform/search is interested in this. If yes I can work on it.
Discussed with Benno. Searching for spelling errors sounds odd especially since we already report them while typing. We should handle this like any other problem being reported in the Problems view along with quick fixes and even multi-quick fixes. Hence the right approach is to add a builder that reports the spelling problems as markers.
*** Bug 314042 has been marked as a duplicate of this bug. ***
*** Bug 318677 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > Reason: I'm spell checking the help at the moment, which means I have to open > each file in an editor, which is pain full. This is indeed painful! (even though we do this only once or twice a year). (In reply to comment #4) > Discussed with Benno. Searching for spelling errors sounds odd especially since > we already report them while typing. We should handle this like any other > problem being reported in the Problems view along with quick fixes and even > multi-quick fixes. Hence the right approach is to add a builder that reports > the spelling problems as markers. We also have 'Find broken externalized strings' in JDT which finds problems on demand. Adding a builder would mean that spelling problems are reported all the time, which means workspace build time would increase something I do not want. Unless of course the spell check builder can be turned on and off... :)
> Unless of course the spell check builder can be turned on and off... :) Every builder can be turned off, see project properties > Builders.
(In reply to comment #8) > > Unless of course the spell check builder can be turned on and off... :) > Every builder can be turned off, see project properties > Builders. I see. I was looking for a workspace wide setting...
*** Bug 433468 has been marked as a duplicate of this bug. ***
*** Bug 471159 has been marked as a duplicate of this bug. ***
A project wide spellcheck would be really useful. When you pickup legacy code a global search would be really helpful.
