![]() ![]() Once installed, I went over all the pages and applied the relevant fixes. Here’s my installation in case it’s useful to someone. With languagetool in the arch repos, that was a no-brainer deal, even if was a bit of a pain to set up. The languagetool extension for VSCode has an additional option called “managed”, where it will start up the server locally on your machine as and when you need it, so long as it’s installed. I’d intended to just run it myself on a server, but that would require internet access which isn’t ideal. languagetoolis designed to run as a service, either using the public hosted one, or running it yourself. It does do some built in spell checking, but it’s not quite good enough to replace code-spell-checker. The tool I settled on was languagetool, which closely resembles Grammarly. Grammar checking was the one I’ve added most recently, and realized the grammar in some of my posts is shockingly bad! ![]() It’s not perfect, and there are words it doesn’t understand but really should, but it’s good enough for me! #Grammar check It runs really quickly and works for both regular text and source code files, which makes spotting typos in code much easier. To check spelling, I use code-spell-checker. What I really want is something automated to do it for me. It’s rare I’ll actually go back over something and fully check its grammar, unless there’s a very obvious issue or typo. Most of my time is spent in either VSCode or QOwnNotes, neither of which have any kind of spelling and grammar checking. Whether it be coursework, blog posts, or any other random thing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |