From: Ihor Radchenko <yantar92@posteo.net>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Grammar checking
Date: Sat, 01 Apr 2023 13:32:05 +0000 [thread overview]
Message-ID: <87lejbg23u.fsf@localhost> (raw)
In-Reply-To: <e6f1e9fe-e108-7ac5-ecc0-8f29a8e10f9e@mavit.org.uk>
Peter Oliver <p.d.oliver@mavit.org.uk> writes:
> On Sat, 1 Apr 2023, Ihor Radchenko wrote:
>
>> Note, however, that Languagetool also has command line interface.
>
> Which, as is discussed elsewhere in the thread, is terribly inefficient.
And, as I followed up, my statement about terribly inefficient might not
hold. It was quite fast in my test with compat manual.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-04-01 13:32 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 7:46 Grammar checking Payas Relekar
2023-03-31 11:20 ` Eli Zaretskii
2023-03-31 12:55 ` Ihor Radchenko
2023-03-31 13:11 ` Eli Zaretskii
2023-03-31 13:29 ` Ihor Radchenko
2023-03-31 14:19 ` Eli Zaretskii
2023-04-02 3:11 ` Richard Stallman
2023-03-31 12:59 ` Gregory Heytings
2023-03-31 13:20 ` Eli Zaretskii
2023-03-31 13:59 ` Gregory Heytings
2023-03-31 14:28 ` Eli Zaretskii
2023-03-31 14:24 ` Ihor Radchenko
2023-03-31 14:39 ` Eli Zaretskii
2023-04-01 6:52 ` Ihor Radchenko
2023-04-01 7:00 ` Eli Zaretskii
2023-04-01 7:10 ` Ihor Radchenko
2023-04-01 7:14 ` Eli Zaretskii
2023-04-01 13:09 ` Peter Oliver
2023-04-01 13:17 ` Ihor Radchenko
2023-04-01 13:24 ` Peter Oliver
2023-04-01 13:32 ` Ihor Radchenko [this message]
2023-04-01 13:42 ` Eli Zaretskii
2023-04-01 13:41 ` Eli Zaretskii
2023-04-03 13:02 ` Peter Oliver
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 5:52 grammar checking Pedro Andres Aranda Gutierrez
2023-04-03 13:51 ` Eli Zaretskii
2023-04-03 15:01 ` Pedro Andres Aranda Gutierrez
2023-03-31 10:03 Grammar checking Payas Relekar
2023-03-29 3:00 jinx Richard Stallman
2023-03-29 22:46 ` jinx Michael Eliachevitch
2023-03-31 4:29 ` jinx Richard Stallman
2023-03-31 6:51 ` jinx Eli Zaretskii
2023-03-31 7:10 ` jinx Gregory Heytings
2023-03-31 7:15 ` Grammar checking (was: jinx) Eli Zaretskii
2023-03-31 7:47 ` Grammar checking Philip Kaludercic
2023-03-31 8:09 ` Gregory Heytings
2023-03-31 8:38 ` Philip Kaludercic
2023-03-31 9:02 ` Gregory Heytings
2023-03-31 11:37 ` Lynn Winebarger
2023-03-31 12:01 ` Gregory Heytings
2023-03-31 12:45 ` Peter Oliver
2023-03-31 15:29 ` Philip Kaludercic
2023-03-31 17:00 ` Peter Oliver
2023-03-31 12:54 ` Peter Oliver
2023-03-31 13:09 ` Gregory Heytings
2023-03-31 11:23 ` Eli Zaretskii
2023-03-31 12:12 ` Peter Oliver
2023-03-31 15:25 ` Philip Kaludercic
2023-03-31 8:40 ` Nasser Alkmim
2023-03-31 8:45 ` Michael Eliachevitch
2023-03-31 13:44 ` Felician Nemeth
2023-03-31 16:03 ` Peter Oliver
2023-03-31 8:48 ` Gregory Heytings
2023-04-01 12:59 ` Lynn Winebarger
2023-04-01 13:18 ` Gregory Heytings
2023-04-01 13:37 ` Eli Zaretskii
2023-04-01 17:30 ` Lynn Winebarger
2023-04-01 17:35 ` Eli Zaretskii
2023-04-02 3:12 ` Richard Stallman
2023-04-02 15:24 ` Lynn Winebarger
2023-04-03 3:05 ` Richard Stallman
2023-04-03 3:05 ` Richard Stallman
2023-04-06 12:29 ` Lynn Winebarger
2023-04-08 3:28 ` Richard Stallman
2023-04-08 13:33 ` Lynn Winebarger
2023-04-08 13:23 ` Eli Zaretskii
2023-04-08 3:28 ` Richard Stallman
2023-04-08 15:20 ` Lynn Winebarger
2023-04-19 5:13 ` Richard Stallman
2023-04-09 9:02 ` Philip Kaludercic
2023-04-09 12:31 ` Lynn Winebarger
2023-04-22 2:22 ` Richard Stallman
2023-04-23 2:25 ` Richard Stallman
2023-04-23 14:14 ` Lynn Winebarger
2023-04-08 3:28 ` Richard Stallman
2023-04-08 14:23 ` Lynn Winebarger
2023-03-31 10:59 ` Eli Zaretskii
2023-04-02 3:11 ` Richard Stallman
2023-04-02 3:40 ` Emanuel Berg
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=87lejbg23u.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=p.d.oliver@mavit.org.uk \
/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.