screenkey VS mini.nvim

Screenkey

That's screen key

Would http://carnackeys.com/ do for you? If you prefer a commercial solution https://www.recmaster.net/how-to/show-keystrokes-while-screen-recording-2 might be of interest, unless you want to switch to Linux and use https://gitlab.com/screenkey/screenkey

Not the exact solution but you can try screenkey

the app I'm making is basically a screenkey clone ( but would ideally be cross-platform ) and to get the app to show the keys the user is pressing I need global keyboard events so the user doesn't have to focus the window to get it to work ( like what winit does ),

You mean an on-screen display for keyboard input? screenkey, no idea about using it with OBS though.

There are tools like Screenkey1 that show every key you press. I'm however not aware of a tool that specifically only shows pressed keys that are bound in sxhkd.

Thanks for the kind words! The app I'm using here is called screenkey

Screenkey (https://gitlab.com/screenkey/screenkey) is a few thousand lines of python for a simple overlay showing the keys you just pressed, are there any less sucky alternatives?

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone