iamcco/diagnostic-languageserver

[Question]: Exit Linter Daemon on Buffer Close

Open

#75 opened on Oct 15, 2021

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (30 forks)github user discovery
help wanted

Repository metrics

Stars
 (437 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Investigate the daemon lifecycle in diagnostic languageserver and explore how to automatically stop the daemon when a buffer is closed. Look at Vim/Neovim autocmd events like BufWipeout or BufUnload to trigger daemon shutdown.
Tech stack
typescript
Domain
developer experiencecli
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60