-
which-key.nvim
đź’Ą Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
wasavi
wasavi is an extension for Chrome, Firefox, and Opera. wasavi changes a textarea element to virtual vi editor which supports almost all the vi/ex commands.
But again, that's not a specifically vim issue, its endemic to TUIs (hence bash completions and all the other hacks to make discoverability accesible). As well, there are some projects to ameliorate this in vim like the which-key family of plugins01 and others like them.
But again, that's not a specifically vim issue, its endemic to TUIs (hence bash completions and all the other hacks to make discoverability accesible). As well, there are some projects to ameliorate this in vim like the which-key family of plugins01 and others like them.
https://github.com/akahuku/wasavi , i'm not sure if this still works, i haven't used it for a while.
I don’t think either currently allows defining those on top of the extension, but you could in the extension itself. Or write it as a plugin extension, effectively, and bind it to whatever you want.
A staple for my (neo)vim config ever since I found it and is absolutely essential is vim-surround. It adds a surroundings “object” as s. It allows you to changes quotes, parentheses, XML/HTML tags, etc.