preservim / vim-wordy

Uncover usage problems in your writing
Other
716 stars 23 forks source link

Alternatives in other programs #26

Open vatrat opened 7 years ago

vatrat commented 7 years ago

I've used vim-wordy in neovim, and I found it to be exceptional. However, I have since moved to Spacemacs (an emacs configuration set up to be similar to vim, but more extensible and with more features set up by default). I can't (haven't found) any similar usage analyzers for emacs, or any other programs. As well, I would like to recommend to some friends who don't know about things like vim a writing analyzer which will work with Microsoft Word and similar word processors. Do you know of anything?

vatrat commented 7 years ago

Can't find (haven't found)*

reedes commented 7 years ago

There was an external java-based analyzer I had tried before creating wordy. It might still be around and usable with emacs. Sorry, I can't recall the name.

vatrat commented 7 years ago

Okay, well thanks. Honestly, I wouldn't be opposed to trying to run an instance of (neo)vim with wordy and feeding data into and out of it back to emacs.

Reed Esau notifications@github.com schrieb am Sa. 5. Aug. 2017 um 17:54:

There was an external java-based analyzer I had tried before creating wordy. It might still be around and usable with emacs. Sorry, I can't recall the name.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/reedes/vim-wordy/issues/26#issuecomment-320474904, or mute the thread https://github.com/notifications/unsubscribe-auth/AL_BBLvG00zI_-v6R2qY2fILP1t-99kGks5sVPKqgaJpZM4OJohx .

vatrat commented 7 years ago

Whoops, left part of the email in.

TiagoSantos81 commented 6 years ago

Hi @reedes,

Some time ago I based my Portuguese analyzers on your work, and even referred to you. I would like to port these English analyzers to LanguageTool as well. I am aware that the license allows me to do it, but I would like to ask your personal permission to do so. Since LanguageTool can be used as a solution inside Emacs, this would also fix this issue. Is it OK to advance with the port?