From: Fossies Administrator <Jens.Schleusener@fossies.org>
To: zsh-workers@zsh.org
Subject: Codespell report for "zsh" (on fossies.org)
Date: Thu, 9 Jan 2020 13:05:13 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2001091252160.17699@fossies.org> (raw)
Hi,
the FOSS server fossies.org - also supporting "zsh" - offers a new feature
"Source code misspelling reports":
https://fossies.org/features.html#codespell
Such reports are normally only generated on request, but as Fossies
administrator I have just created (for testing purposes) an analysis for
the current "zsh" release 5.7.1:
https://fossies.org/linux/misc/zsh/codespell.html
That version-independent (not linked) URL should redirect always to the
last report (if available), so currently to
https://fossies.org/linux/misc/zsh-5.7.1.tar.xz/codespell.html
Just for information there are also two supplemental pages
https://fossies.org/linux/misc/zsh/codespell_conf.html
showing some used "codespell" configurations and
https://fossies.org/linux/misc/zsh/codespell_fps.html
showing all resulting obvious "false positives".
Maybe more meaningful is an additional report for the current Git master
version that can be found in a special "test" folder (that isn't
integrated in the Fossies standard services and should - at least
principally - not accessible by search engines):
https://fossies.org/linux/test/zsh-code-4858e868dcf809016a1cb5680327d66d551353ae.zip/codespell.html
Obviously in that current development version some of the spelling errors
respectively typos are already fixed.
Regards
Jens
--
FOSSIES - The Fresh Open Source Software archive
mainly for Internet, Engineering and Science
https://fossies.org/
next reply other threads:[~2020-01-09 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:05 Fossies Administrator [this message]
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
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=alpine.LSU.2.21.2001091252160.17699@fossies.org \
--to=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).