mattn / mattn/efm-langserver

How can I check the status of an efm linter?

Open
#237 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.6k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

I have a linter which takes a variable amount of time to run (anywhere between 2 seconds and up to 1 minute), and I would like to have some way of distinguishing between 'linting done, no errors' and 'linting still busy'.

So I made a wrapper which I pass instead of the actual linter, that outputs 'Warning: linter started' first, then runs the actual linter, and then outputs 'Warning: linter finished' and that works once - but since the warnings are persistent and remain visible until a fresh linter execution finishes, the 'linter finished' message from the previous run remains visible, so I still can't tell if the current linter execution is finished after each edit to the file.

Note I originally posted this on vim stackexchange but someone suggested it fits better here and I agree.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing efm-langserver's linter execution and warning publication behavior. Determine whether the server exposes a per-run completion signal or whether the request requires a new status mechanism; done means a client can distinguish the current lint run from a previous run with no errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.