From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: gregory@heytings.org, relekarpayas@gmail.com, rms@gnu.org,
m.eliachevitch@posteo.de, emacs-devel@gnu.org
Subject: Re: Grammar checking
Date: Sat, 01 Apr 2023 10:14:17 +0300 [thread overview]
Message-ID: <83tty0ysza.fsf@gnu.org> (raw)
In-Reply-To: <87zg7sf57l.fsf@localhost> (message from Ihor Radchenko on Sat, 01 Apr 2023 07:10:22 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: gregory@heytings.org, relekarpayas@gmail.com, rms@gnu.org,
> m.eliachevitch@posteo.de, emacs-devel@gnu.org
> Date: Sat, 01 Apr 2023 07:10:22 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Agree. I can also see several related bug reports in their repo.
> >> The question is though whether "not bad" is good enough and who is to
> >> decide what is good enough for Emacs.
> >
> > We get to decide that. Who else?
>
> I was hoping to hear the criteria you have about good enough grammar
> checking.
I gave my opinion. I'm not the only one whose opinion matters, but I
have no control on what others say or don't say. So I'm not sure what
else do you want to hear from me.
> >> I'd be happy if Emacs had a good integrated grammar checking support. Is
> >> there anything else I can help to move this thread forward?
> >
> > Provide a Lisp package to integrate LanguageTool into Emacs in a
> > convenient way?
>
> What is "convenient"? Is there particular must-have functionality?
> Should it be ispell integration? flyspell?
Both, IMO.
> Probably not the latter as it is word-based.
Indeed, it should check larger chunks of text, like sentences or
paragraphs.
> Though ispell.el also appears to rely on word-based paradigm in the
> code.
That's because this is how the spell-checkers work, I believe.
next prev parent reply other threads:[~2023-04-01 7:14 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 [this message]
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
-- 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 14:23 ` Lynn Winebarger
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-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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tty0ysza.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=m.eliachevitch@posteo.de \
--cc=relekarpayas@gmail.com \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).