From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Fossies Administrator" <Jens.Schleusener@fossies.org>
Cc: zsh-workers@zsh.org
Subject: Re: Codespell report for "zsh" (on fossies.org)
Date: Thu, 09 Jan 2020 17:38:43 +0000 [thread overview]
Message-ID: <a16e37ee-ccf7-4154-9ed7-a435f2f8f430@www.fastmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2001091517310.7580@fossies.org>
Fossies Administrator wrote on Thu, 09 Jan 2020 14:54 +00:00:
> Fossies Administrator wrote on Thu, Jan 09, 2020 at 13:05:13 +0100:
> > Is it possible to get the report in the form of a unidiff?
...
> So a vague idea was to make the spelling errors selectable and then to
> create multiple (or even one) unidiff files
I just used «git add -p» to pick and choose which changes to
stage/commit and which not to. (Specifically, I used «git -c
interactive.diffFilter="perl /usr/share/doc/git/contrib/diff-highlight/diff-highlight"
add -p» in order to have «git add -p» show me wordwise diffs.) When
that command finished, I reviewed «git diff --word-diff --cached»,
committed it, and reverted the local changes (which were the false
positives, etc; I'd made sure I had no local changes before I applied
all the detected typo fixes).
> but that isn't trivial to realize and for e.g. probably not usable by
> projects using GitHub.
Yeah, github doesn't provide a UI for this, AFAIK.
> By the way, the basically used tool "codespell"
> (https://github.com/codespell-project/codespell) offers an option
> "--write-changes" to "write changes in place if possible".
*nod*
Cheers,
Daniel
prev parent reply other threads:[~2020-01-09 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:05 Fossies Administrator
2020-01-09 13:50 ` Daniel Shahaf
2020-01-09 14:54 ` Fossies Administrator
2020-01-09 15:49 ` Mikael Magnusson
2020-01-09 16:43 ` Fossies Administrator
2020-01-09 17:38 ` Daniel Shahaf [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a16e37ee-ccf7-4154-9ed7-a435f2f8f430@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--cc=Jens.Schleusener@fossies.org \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).