iamcco / iamcco/diagnostic-languageserver

[Question]: Exit Linter Daemon on Buffer Close

Open
#75 0 comments 1 reaction 0 assignees View on GitHub
help wanted
Dominant language
TypeScript
Stars
439
Forks
30
PR merge metrics
No merged PRs in 30d

Description

I'm using `eslint_d` with the configuration below. The issue I'm running into is that once a daemon is started for a particular file/buffer, it is not closed when the buffer is closed. This results in a large number of `node` processes running continuously on my machine (which I have to `pkill` on a regular basis).

Is there a good way to trigger the linter to exit when a buffer closes? I'm guessing this is not an issue for other linters as they don't (to my knowledge) run as daemons.

Thanks for any help in advance!

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files, tests, or entry points are mentioned. Start by tracing how eslint_d is started for a buffer and how buffer-close events are handled; done means establishing whether the daemon can be stopped on close and documenting or implementing the supported lifecycle behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.