all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Oliver <p.d.oliver@mavit.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yantar92@posteo.net, emacs-devel@gnu.org
Subject: Re: Grammar checking
Date: Mon, 3 Apr 2023 14:02:13 +0100 (BST)	[thread overview]
Message-ID: <fc5062ad-9a6c-1e1a-a26f-4b8ed2a1ad7c@mavit.org.uk> (raw)
In-Reply-To: <83wn2vyb1u.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

On Sat, 1 Apr 2023, Eli Zaretskii wrote:

>> Date: Sat, 1 Apr 2023 14:24:24 +0100 (BST)
>> From: Peter Oliver <p.d.oliver@mavit.org.uk>
>> cc: emacs-devel@gnu.org
>>
>> 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.
>
> Since when is subprocess communications "outlawed" in Emacs for
> significant features that need to have good performance?

I wasn’t aware that anyone here was advocating that.

> Also, linking against a library instead of communicating with a
> program has its disadvantages as well: if the library crashes, so does
> Emacs.

I think you’ve got this thread confused with the one about Jinx, which uses the Enchant library for spellchecking.

In this thread, I have said that I believe that we could benefit from LanguageTool offering some IPC mechanism other than TCP.

OTOH, AIUU, Ihor believes that, rather than running LanguageTool persistently, it is tolerable to exec “java -jar languagetool-commandline.jar /path/to/file/to/be/checked” on each occasion that you wish to check some text.  The downside to this is that it takes many CPU-seconds for it to initialise before it can do any actual checking, and you pay that initialisation cost every time.

-- 
Peter Oliver

  reply	other threads:[~2023-04-03 13:02 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
2023-04-01 13:42                     ` Eli Zaretskii
2023-04-01 13:41                   ` Eli Zaretskii
2023-04-03 13:02                     ` Peter Oliver [this message]
  -- 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=fc5062ad-9a6c-1e1a-a26f-4b8ed2a1ad7c@mavit.org.uk \
    --to=p.d.oliver@mavit.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@posteo.net \
    /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.