In-line ignoring of the following line

[spetrosi]

Sometimes it is not convinient to write a codespell ignore comment on the line that I want to ignore.
Other linters allow for writing the ignoring comment above the to-ignored line.

So instead of doing this and as a result have a very long string:

                mode: "0644"
                regexp: "^(options|blacklist) {{ item }}"  # codespell:ignore blacklist

I want to be able to do this:

                mode: "0644"
                # codespell:ignore blacklist
                regexp: "^(options|blacklist) {{ item }}"

[fregante]

This is required in formatted codebases (black, prettier, biome). I had to disable codespell on whole files for this.

Related:

• support ignore for blocks of code #3381

[DimitriPapadopoulos]

Why is this required in formatted codebases?

Trying to find a solution here: How do linters handle # noqa in such cases?

[fregante]

It's required because the formatter will place any comments on the following line when they no longer fit. So

console.log("60 characters fo sho"); // codespell:ignore fo

I formatted as

console.log("60 characters fo sho"); 
// codespell:ignore fo

This means I cannot ignore certain words unless I exclude the whole file from codespell or word from the entire project.

Eslint has // eslint-disable-next-line

[DimitriPapadopoulos]

It might be seen as a formatter issue as well, as this is the first time this is reported. I suspect codespell is mostly used by Python programmers, and Python formatters might a better job at handling linter directives. Your proposal makes sense, though, it might avoid long lines and result in more readable code.

I feel codespell:ignore-next-line is a bit long, how about codespell:ignore-next?

In any case, this could probably be fixed without too much performance penalty or additional complexity. PRs welcome.