Proposal: mini.run and mini.outline (willing to implement)

[ChristopherBilg]

Hi everyone,

I've been using the mini plugins for about a year now and want to start giving back to the project. I'm a software engineer and rely on these tools daily, so I'm ready to build both modules if they align with the project's direction.

Here are the two ideas:

1. mini.run (Lightweight Task Runner)

   I'm looking for a simple local task runner. Tools like stevearc/overseer.nvim and Zeioth/compiler.nvim are great, but they often feel too heavy for a standard workflow.

   • Goal: Read a local config (like .vscode/tasks.json or a Lua equivalent) to execute project-specific scripts.
   • UI: Run tasks in the background with a toggleable split or floating window to check output streams and exit codes.
   • Simplicity: A fast way to compile or run code without a large dependency tree.

2. mini.outline (Symbol Hierarchy Sidebar)

   Having a unified outline window makes navigating large files much easier.

   • Goal: A simple vertical split showing the hierarchy of the current buffer (functions, classes, methods, loops).
   • Navigation: Pressing or clicking a node jumps the cursor to the definition.
   • Integration: Relies entirely on Neovim's native LSP document symbols or Treesitter queries to map the structure.

Let me know what you think of these concepts and if you would be open to discussing either (or both!) of these further.

[krovuxdev]

I was already planning that
mini.run -> #1123
mini.hierarchy -> #2394

[echasnovski]

Thanks for the suggestion and enthusiasm!

As pointed out in this comment, both of these functionalities were already suggested earlier and are planned to be a part of 'mini.nvim'. At this point in time, I prefer to implement all new modules myself with the help of the other MINI team members.

[ChristopherBilg]

Thank you both! I was using the "Planned modules" section of the main .org website as a list of what to check so I didn't know these were already planned, my apologies.

[echasnovski]

No worries! It's on me to not have that list up to date. Those are the modules about which I am more or less certain that they will be added. If the module is not there, it means that either it was not my idea initially or there are doubts about the feasibility of the module implementation with 'mini.nvim' design constraints.

You can see other suggested modules in issues with a dedicated label.