[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57613] Codespell report for "Octave" 5.1.90 (

From: anonymous
Subject: [Octave-bug-tracker] [bug #57613] Codespell report for "Octave" 5.1.90 (on fossies.org)
Date: Thu, 16 Jan 2020 15:16:46 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0


                 Summary: Codespell report for "Octave" 5.1.90 (on
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Thu 16 Jan 2020 08:16:45 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Jens Schleusener
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any



The FOSS server fossies.org <https://fossies.org/> - also supporting the
latest Octave release <https://fossies.org/linux/octave> - offers a new
feature "Source code misspelling reports"

Such reports are normally only generated on request, but as Fossies
administrator I have just created (for testing purposes) an analysis for the
current development version Octave 5.1.90.

Since development versions are not normally supported by Fossies I have put it
in a special "test" folder (that isn't integrated in the Fossies standard
services and should - at least principally - also not accessible by search



Although after a first review some obviously wrong matches ("false positives")
are already filtered out (ignored) please inform me if you find more of them
so that I can force a new improved check if applicable.

Just for information there are also two supplemental pages


showing some used "codespell" configurations and


showing all resulting obvious "false positives".

And two small remarks:

All files in the directory "OLD-ChangeLogs" were ignored (excluded) since they
are containing many spelling errors but are probably no longer interesting for
possible spelling corrections (but if so please let me know).

Unsure I was about the word "indicies" at line 263 and 268 of the file
since in the neighborhood in similar constructs also the suggested word
"indices" is in use (sorry, I'm a C-layman).


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]