hinell

@vuki656 The project is usually opened in a workspace root where `package.json` with `packages: ...` field might be found. So it's not a big deal to check which `package.json` was...

Any chances you add it? Like. This repo is completely obscure to me.

Repo isn't maintained. Checkout alternative: https://github.com/hinell/move.nvim

Would be best if this plugin: * exposes plugin api * telescope integration uses that API to list commands

I also wonder. We should probably resort to `vim.filetype.add` instead... I think we should fill an issue on main `neovim` repo so they update it.

The `help index.txt` is a good starting point I guess.

Well I think you can already filter out commands specific to the `visual`/`selection` mode when activate Legendary: ```lua { mode = { "n", "v", "i" }, "" , function() require("legendary")...

Oh yeah, it's for user cmd... overlooked that.

We need an alternative to `legendary.nvim`; this project along with some others isn't contribution-friendly; please notify me if you want to unite an effort in replacing it.

The problem is that @mrjones2014 have [suggested](https://github.com/mrjones2014/legendary.nvim/pull/415#discussion_r1366850690) (very vaguely) me to implement entire keymaps-like `mode=` api in my #415 PR when it was never intended to do so; I suggested...