From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Grammar checking in Emacs
Date: Sun, 14 Nov 2021 21:46:19 -0500 [thread overview]
Message-ID: <jwv5ysu41b3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m1zgq6xon7.fsf@yahoo.es> ("Daniel Martín"'s message of "Mon, 15 Nov 2021 01:12:44 +0100")
> The question is if those feelings about grammar checking still hold
> true. I think one of the most popular free programs to do grammar
> checking is LanguageTool (https://languagetool.org). I've quickly
> tested it and it detected some non-trivial grammar mistakes, in English
> and Spanish at least. I didn't see false positives, which is a good
> thing in this kind of tools. You can try the tool from its website
> without installing it on your computer.
IIUC (after looking at https://github.com/languagetool-org/languagetool)
this is structured as a grammar-checking server (written in Java) that
can run on a remote host and then client applications connect to it and
presumably send their text to it a bit like they'd do with an LSP
server, except the clients aren't expected to launch the server.
Sadly it's not packaged for Debian (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403619 suggests for
the details). I can't see any info about using it on Fedora either.
AFAICT the most popular way to install it is as a "snap" package, which
I consider to be a euphemism for a blob :-(
> Is there interest in having this feature in Emacs? Perhaps as an ELPA
> package, if the technology is not mature enough to have it in Core?
I think it would be nice to provide a package for such grammar checking,
yes. We should be careful not to encourage users to just connect to
someone else's LaguageTool server, since that would be SaaSS, but other
than that I see no reason not to have such a package in GNU ELPA.
I don't expect many users to have such a server, so it's probably not
widespread enough to justify having it in core, currently.
Stefan
next prev parent reply other threads:[~2021-11-15 2:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1zgq6xon7.fsf.ref@yahoo.es>
2021-11-15 0:12 ` Grammar checking in Emacs Daniel Martín
2021-11-15 2:46 ` Stefan Monnier [this message]
2021-11-15 8:16 ` tomas
2021-11-15 22:43 ` Peter Oliver
2021-11-15 23:02 ` Stefan Monnier
2021-11-16 18:01 ` Philip Kaludercic
2021-11-16 18:09 ` Eli Zaretskii
2021-11-17 3:18 ` Stefan Monnier
2021-11-19 21:51 ` Peter Oliver
2021-11-17 4:13 ` Richard Stallman
2021-11-19 22:14 ` Peter Oliver
2021-11-16 4:06 ` Richard Stallman
2021-11-16 11:32 ` Ihor Radchenko
2021-11-16 14:28 ` Stefan Monnier
2021-11-16 22:49 ` Tim Cross
2021-11-16 23:29 ` Stefan Monnier
2021-11-16 6:28 ` Alexandre Garreau
2021-11-16 14:30 ` Stefan Monnier
2021-11-16 15:43 ` tomas
2021-11-18 3:51 ` Richard Stallman
2021-11-16 8:23 ` tomas
2021-11-15 19:45 ` Rudolf Adamkovič
2021-11-17 4:12 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv5ysu41b3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.