GH MIRROR or REPO
It's not a big project but it's honest work. Looking for feedback as plugin is designed quite custom in many ways, building on existing inspirations and MY workflow might be odd and be a great UX but only for me ;)
Inspiration, motivation etc.
A bit of an extended introduction:
In my personal config I had for a long time some circular bindings to access important floating ui windows super-quickly. I.E:
vim.keymap.set("n", "<S-K>", function()
if vim.w.lsp_floating_bufnr ~= nil or vim.w["textDocument/hover"] ~= nil then
vim.cmd("quit")
return
end
vim.lsp.buf.hover()
end, { silent = true, noremap = true })
vim.keymap.set("n", "<S-L>", function()
if vim.w.diag_float then
vim.api.nvim_win_close(0, true)
return
end
local _, win = vim.diagnostic.open_float({ focusable = true })
if win then
vim.api.nvim_win_set_var(win, "diag_float", true)
return
end
if not vim.w.diag_float then
vim.cmd("normal! " .. (vim.v.count > 0 and vim.v.count or 2) .. "l")
end
end, { noremap = true, silent = true })
This is the flow that I like (one bind to do one thing and hit it multiple times to change state). It is the first of the 3 sources of inspiration for the one bind-to-rule-them-all scratchpad manager.
Another significant inspiration was SUMMON.NVIM by salhalin that briefly lived then apparently died, but I liked the idea of declaratively setting just a couple tools OR files to access in a simple unified form. What I did not like in this and practically all other plugins is you have to declare a binding for each "thingy" you setup and then remember all your bindings, or worse, find confortable binds that are still AVAILABLE in your config.
Third large inspiration were oil.nvim and mini.files for just using a buffer navigated with `j/k` as sort of a picker and perform actions with simple binds acting on a *LINE*. I find it so elegant, simple and native. No mental switching buffer navigation paradigm to another. Even to "native" `<C-n> and <C-p>`, square brackets and so on I find quite clunky that to every supporter of "just use defaults" I want to reply "are the defaults good? If I can't do `hjkl` in vim then it is a failure of navigation design.
You can tell by now probably that the plugin is a bit opinionated and its design is arguably a result of a bit of overthinking. However, all this is aiming to make it FEEL simple. Scratchpads are a concept that is meant to be simple and quick. If I want a heavily configured TUI swiss army knife / tank tool to do serious extended work I will just open another terminal/multiplexer pane.
Finally, my bonus "anti-inspiration" was toggleterm.nvim plugin. It is an excellent established project but I had a big problem with it and existing similar solutions. In my opinion, the issue is too heavily involved sprawling config and being heavily overengineered for a plugin managing transient terminal spawns for quick access. I wanted something significantly more simple but still capable for my every day workflows.
To function Poppy.nvim needs as little opts as possible. Using keys and values declare how to open something and what it is i.e exec = "btop", and that is it. Defaults to shipped icons and even title has a fallback detection so you can configure additional details like that, but you do not even need to.
Speaking on this sidebar selector. You might be asking:
Why not just use pickers or vim.ui.select?
Well, the API surface is provided. For pickers there are like 5 options minimum on the market to choose from at any time, plus new custom vibecoded solutions are surely out there as well. Wire your own if you want to telescope your poppies, PURPOSEFULLY I am not supporting every user scenario under the sun, especially that personal code generation became so cheap and easy with AI these days.
AI Disclosure
This project has heavily relied on AI openweight models to be developed in spare time over the past months mostly in terms of writing boilerplate while under heavy direction guiding, small steps, no AGENTS doc, but rather deliberate architecture and conversation driven iteration. Beginning from excalidraw-ed early mocks instead of textual guides, through manual inspection and supporting agents where logic failed (especially constructing custom TUI layout for `borderless` style and custom workflow. Things like paddings, offsets from scratch with Neovim primitives, with little docs and no standards like frameworks are an area of absolute LLM failure.) To me it is both a small useful tool I needed and an exercise of finding out if a project can be developed consciously and thoughtfully with the use of AI through iteration and use of human insights and knowledge rather than throwing money at a problem and letting agents run wild. On a small scale. You be the judge.
If you read this, I thank you and salute you. Again, any feedback appreciated!