Dominique Pellé

This issue is a bit old. Can you try again with the latest version of the plugin? For me, it works fine with vim-8.2.3223 as well as noevim v0.6.0-dev+81-gc642f3ac2 on...

I merged into thee master branch PR which is meant to fix this plugin for Windows: https://github.com/dpelle/vim-Grammalecte/pull/27 Can you try again if your problem is now fixed?

Barichard wrote: > Hi, > This plugins seems very nice. Unfortunately, I have an issue with the > scratch window. When I use GrammaclecteCheck, it highlights errors in my >...

@ArchangeGabriel a écrit : > Les erreurs d’orthographe (ou mots inconnus du dictionnaire) ne sont reportés > que par changement de couleur dans la fenêtre principale, tandis que la fenêtre...

I don't know yet why you see this error. Can you provide the versions that you use for Grammalecte and Vim (output of :version)? I don't have Windows (I use...

I just downloaded the latest Grammalecte 0.5.17 and it works fine for me with Vim-8.628 on Linux and the latest vim grammalecte plugin from github (fffc6762c1929bd17eb1dfce966d609df4658245). I'll have to spend...

I should have time to try the vim-Grammalecte plugin on a Windows 7 machine this coming weekend. In the mean time, something worth trying: you could hard-code the full path...

Thanks @ledshark24 for digging into this. Not having Windows, I was in the dark as I could not reproduce the issue. I understand that it's not not entirely right on...

I'm not sure where and why you would want to use @Spell and @NoSpell. The vim-Grammalecte plugin does not use vim spelling checker. All highlighting (grammar errors and spelling errors)...

> I write a lot of markdown with blocks of code inside. Oh I now see. Yes, checking only text with @Spell would be very useful. Well, @Spell may not...