emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: "Juan Manuel Macías" <maciaschain@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix some typos
Date: Thu, 23 Sep 2021 12:25:55 +0200	[thread overview]
Message-ID: <87o88jd1vw.fsf@gmail.com> (raw)
In-Reply-To: <f117f9d7-a465-311b-55d2-2af4e657d7ee@gmail.com> (Max Nikulin's message of "Wed, 22 Sep 2021 23:47:12 +0700")

Max Nikulin <manikulin@gmail.com> writes:

> Please, forgive my ignorance of Shakespeare's poetry.

Ignorance is bliss!  (Sophocles)

> On 17/09/2021 17:05, Marco Wahl wrote:
>>> On 17/09/2021 04:40, Stefan Kangas wrote:

>>>> Please find attached another clean-up patch that fixes a small
>>>> number of typos. > > Thou shall not change "memeory" to "memory" tho

> I think, a bit more is required to avoid recurring attempts to change
> spelling if you would like to see such variant. Static code analyzers
> usually have a feature that allows to ignore specific warning at a
> particular line, see e.g.
> https://flake8.pycqa.org/en/latest/user/violations.html#in-line-ignoring-errors
> for Python's flake8.
>
> Maybe "LocalWords:" could do a similar trick for ispell.el at least for
> the whole file. Unsure if it is possible to add an exception for the
> quote only.

Interesting ideas!  

> However there is namely "memory" in the "1609 Quarto", see e.g.
> https://en.wikipedia.org/wiki/Sonnet_1 Web pages with the same variant
> as in the Org manual do not mention the source (particular edition). I
> hope, I just do not know what is considered as the canonical variant for
> not so old language.

Same here.  I have no idea.

What I found suspicious, was the correction occurring in a quote
section.  But you are right.  Since there is no reference to the source
the correction is worthy AFAICS.

If I'd be the only committer, I'd leave the "memeory" anyway.  But go
ahead and change the occurance to "memory" if you like.  I won't try to
stop you.







      parent reply	other threads:[~2021-09-23 10:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 21:40 [PATCH] Fix some typos Stefan Kangas
2021-09-17  9:03 ` Timothy
2021-09-17 10:05   ` Marco Wahl
2021-09-17 10:26     ` Stefan Kangas
2021-09-22 16:47     ` Max Nikulin
2021-09-22 20:18       ` Juan Manuel Macías
2021-09-23 14:49         ` Max Nikulin
2021-09-24  6:03           ` Loris Bennett
2021-09-24 12:23             ` Juan Manuel Macías
2021-09-25 11:08               ` Marco Wahl
2021-09-29 10:34                 ` Max Nikulin
2021-09-29 11:09                   ` Marco Wahl
2021-09-29 11:11                   ` Bastien Guerry
2021-09-25 11:47               ` [PATCH] org-manual.org, ORG-NEWS: fix Shakespeare' sonnet and another, typo Max Nikulin
2021-09-29 11:14               ` [PATCH] Fix some typos Bastien
2021-09-23 10:25       ` Marco Wahl [this message]

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o88jd1vw.fsf@gmail.com \
    --to=marcowahlsoft@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    --cc=manikulin@gmail.com \
    /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/org-mode.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).