All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: Kees Cook <keescook@chromium.org>,
	Andy Whitcroft <apw@canonical.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch: Avoid missing typo suggestions
Date: Thu, 04 Jun 2020 00:29:36 -0700	[thread overview]
Message-ID: <97eb5b4e4db4b50462032b1da0788dd61ed0a30e.camel@perches.com> (raw)
In-Reply-To: <CAD8XO3bezWoM7Pc0VoiFgoDWTLMN6VwV1vEFL7PR=_iohV82Ag@mail.gmail.com>

On Thu, 2020-06-04 at 09:55 +0300, Maxim Uvarov wrote:
> On Thu, 4 Jun 2020 at 03:39, Joe Perches <joe@perches.com> wrote:

Hi Maxim.

> > btw: My codespell dictionary file moved to
> > /usr/lib/python3/dist-packages/codespell_lib/data/dictionary.txt
> > 
> > and I had to use --codespell --codespellfile=(above) so
> > maybe there should be multiple lookups for this file
> > like the array below.
> > 
> > Are there other standard codespell dictionary locations?
> 
> It might be better to support standard and non standard locations.

It already does with the --codespellfile=<location> opti.

> I think it's better to request from codespell where his dictionary is.

Maybe a good idea, but looking at the codespell git, for
versions 1.17 on there are several standard dictionaries.
https://github.com/codespell-project/codespell/tree/v1.17.1/codespell_lib/data

> I created ticket for this:
> https://github.com/codespell-project/codespell/issues/1540

Even if codespell is updated, the script would have to deal
with older versions that don't support requesting that option.

cheers, Joe



  reply	other threads:[~2020-06-04  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 23:19 [PATCH] checkpatch: Avoid missing typo suggestions Kees Cook
2020-06-04  0:39 ` Joe Perches
2020-06-04  6:55   ` Maxim Uvarov
2020-06-04  7:29     ` Joe Perches [this message]
2020-06-04 14:45       ` Maxim Uvarov
2020-06-04 22:08   ` Kees Cook
2020-06-05  1:02     ` Joe Perches
2020-06-05  3:05       ` Kees Cook

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=97eb5b4e4db4b50462032b1da0788dd61ed0a30e.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxim.uvarov@linaro.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. 
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.