nvim-mini / nvim-mini/mini.nvim
mini.run: simple run configs manager in your editor
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 9.5k
- Forks
- 310
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 1
Description
Contributing guidelines
- I have read CONTRIBUTING.md
- I have read CODE_OF_CONDUCT.md
Module(s)
mini.run
Description
One of the most basic features of most code editors or IDEs is running your code from the editor and getting back the errors. Yet, there aren't many popular or simple options to do this in neovim apart from overseer.nvim.
Features :
- Easily define run configs for specific languages
- For example you're working in rust : create a "Build", a "Run" config and a "Test" config
- Easily define run configs for specific projects
- Using a directory name matching or finding a specific file in the working dir, you can have a "Run Server" and "Run Client" config for your game
- Watch for interpreted languages runtime errors or crashes and log them to qflist dynamically
- So if your Node http server throws an exception you can quickly fix it
- Compile errors, runtime errors or interpreter errors are logged back to your quickfix list so you can easily code-compile-code
- You can configure an optional command to choose if an integrated terminal should be open (example: "30vsplit term" to open a vertical terminal)
Bonus:
- Composite configs? (run multiple configs at once)
- DAP integration? (use the same menu for custom run configs and dap debug configs)
I think this idea really fits into mini's philosophy of small, straightforward and simple plugins, and probably fills a void in the neovim plugin ecosystem. I am willing to try and make a PR for a MVP of that new module.
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
Start with CONTRIBUTING.md and the mini.run proposal in this issue; no implementation files or tests are identified. Before coding, define the MVP scope, configuration model, project detection, error handling, terminal behavior, and success criteria, then inspect existing mini.nvim module conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100