nvim-flutter / nvim-flutter/flutter-tools.nvim
[Feature Request] Kill attached flutter processes on nvim exit
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 1.4k
- Forks
- 116
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
A simple and small but potentially resource saving feature, as it's sometimes easy to forget to quit flutter processes before exiting nvim.
Whenever exiting nvim, stop any current attached flutter processes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the plugin's Neovim exit handling and the code that tracks attached Flutter processes. Done means exiting Neovim stops any currently attached Flutter processes without affecting unrelated processes; verify the behavior with the existing test setup if one covers process lifecycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, lua, neovim
- Domain
- mobile-dev, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100