all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: grammar checking
Date: Mon, 3 Apr 2023 17:01:15 +0200	[thread overview]
Message-ID: <CAO48Bk8QZin+pMy0Z0DU6VZS4X5JbVk2RQ8CzG+PGcS1gCt0=Q@mail.gmail.com> (raw)
In-Reply-To: <831ql1vzua.fsf@gnu.org>

Eli writes:

> From my POV, if people who write doc strings and manual submissions
> for Emacs will be able to have their text proof-read before they
> submit it, it will be an advantage, since the patch reviewers will
> need to invest less time in finding and fixing their grammar mistakes

That could be a valid point, since docstrings require a certain style and
a reduced grammar. But I'm just a frustrated potential user ;-)

> (although probably not in your submissions).

Thanks for the trust, but read them N times before accepting them. As I said,
grammar checking and proof-reading come hand in hand and cost time.
I'm the first to blush at some things I write when on a hurry or overexcited

;-)
/PA

On Mon, 3 Apr 2023 at 15:50, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> > Date: Mon, 3 Apr 2023 07:52:23 +0200
> >
> > 1. I have worked with different word processors that provide grammar
> > checking in addition to spellchecking. At the end of the day, I had to
> > ignore 49 suggestions to accept a good one, which I would have caught
> > with reasonable proof-reading. Writing is something that needs time.
> > And I feel it every day, even for technical writing. And there are no
> > shortcuts to that.
> >
> > 2. I have tried grammar checking on different languages. Yes, I speak
> > a couple of languages and I write fluently in four. And at the end, I
> > either disable grammar checking or I just leave it there for fun. Some
> > suggestions are as good as spellchecking was 20 years ago. And a good
> > laugh may be worth it, but seriously, I'd rather not use grammar
> > checking when in a hurry.
> >
> > 3. I'm honoured to count professional writers and journalists among my
> > friends and, no, they don't use grammar checking ;-) because they feel
> > the tools currently force them into a style of writing which is not
> > theirs.
>
> That's okay: if this will become part of Emacs, it will be an optional
> feature, so if you don't find it useful, just don't activate it.  Many
> features in Emacs exist only for those who find them useful, and this
> one is no exception.
>
> From my POV, if people who write doc strings and manual submissions
> for Emacs will be able to have their text proof-read before they
> submit it, it will be an advantage, since the patch reviewers will
> need to invest less time in finding and fixing their grammar mistakes
> (although probably not in your submissions).
>
> > I feel it would be more urgent to concentrate on spellchecking and see
> > how to improve support for languages with word composition on current
> > solutions in core Emacs or packages in ELPA.
>
> We will continue developing and improving our spell-checking features
> independently of whether grammar checking will or will not be added.
> There's no zero-sum game here; these are two separate features, and
> none of them will come at the expense of the other.



-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
run a leader-deposed hook here, but we can't yet



  reply	other threads:[~2023-04-03 15:01 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-31 10:03 Grammar checking Payas Relekar
2023-03-31  7:46 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
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='CAO48Bk8QZin+pMy0Z0DU6VZS4X5JbVk2RQ8CzG+PGcS1gCt0=Q@mail.gmail.com' \
    --to=paaguti@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.