Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

linter output format is not standardized

See original GitHub issue

The standard format for linters is file-path:line:column but cspell is using file-path[line, column], making it incompatible with lots of tools that rely on this.

For example iTerm2 fails to identify correct filename and the semantic-history feature get broken before it tries to open file-path[line instead of file-path.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

Jason3Scommented, Jun 24, 2018

With 3.1.1, this should work as expected.

I tested it with iTerm2, cmd-click will open the expected file and take the cursor to the right location.

I’m going to close for now.

0reactions

github-actions[bot]commented, Aug 15, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

linter output format is not standardized · Issue #35 - GitHub

The standard format for linters is file-path:line:column but cspell is using file-path[line, column], making it incompatible with lots of ...

Formatters - ESLint - Pluggable JavaScript Linter

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

How to format ESLint output. Playing with CLIEngine API

Let's create our own module that will act like normal ESLint but will be able to format the output. npm init{ "name": "formatted-linting",...

JavaScript Standard Style

JavaScript style guide, linter, and formatter. This module saves you (and others!) time in three ways: No configuration. The easiest way to enforce...

Linting and Auto-formatting Ruby Code With RuboCop

Linting is the automated checking of source code for programmatic and stylistic errors. This checking is performed by a static code analysis ...