Firenvim – Turn the browser into a Neovim client
github.com
github.com
In theory someone could take nvim, compile it into WASM, and make a version that'll work without interacting with any native binaries (at the cost of some performance and nvim functionality, of course). The only big downside is that you'd lose the integration with the nvim config in your home directory, but perhaps some kind of filesystem API can help with that.
Care to elaborate? What security risks
EDIT: I remembered another issue. I'm not able to use it at work because my employer doesn't allow extensions that access all data on a website.
[1] https://github.com/glacambre/firenvim#building-a-firenvim-sp...
Or maybe give the option to only fall back to this fixed size, fixed position textbox if the box dimensions are smaller than a predefined size.
My use-case is ServiceNow which forces us into their crappy proprietary editor.
But you do need to get good at calibrating which sites get set off by it because as others have said you don't want it going off an every little text prompt you get most likely
From someone acquired by ServiceNow… I hope your stock options are worth it
It doesn't have 100% compatibility with vim - no vimscript, for example - but it covers more than enough of the basic movement commands & mappings to be entirely productive for me. I don't know if I would write actual pages of code in it, but I gratefully use it to write long queries in the browser.
It does, however, work great for me so :fingers-crossed: I can avoid re-shaving this yak for another few years.
Is there a way to completely disable all regular browser shortcuts as well as all key event propagation to the sites themselves, and make Tridactyl the be-all-end-all handler for the keyboard?
If `leavegithubalone` is set to false (the default) and a website can steal a `leavegithubalonekeys` key from Firefox (usually /) then that is a Tridactyl bug. Unfortunately it is a Tridactyl bug that I do not know how to fix :)
For Firefox stealing keys from Tridactyl, you can patch Firefox without rebuilding it as this intrepid bunch describe here
https://github.com/glacambre/firefox-patches/issues/1#issuec...
But also for larger text messages you don't get constrained by the typically small input text fields
In a dreamy ideal world this, of course, would be the kind of basic functionality that any self-respecting OS would offer - in any text input field in any app.
I've had the same experience with things like vim emulation in vscode but I switched to LazyVim from vim a few months ago and it's been a smooth experience for me.
I tend to hit that instead of Esc everywhere I'm using a vi-like after having a weird keyboard issue that nerfed my Esc key for a while (long and uninteresting story) and then finding that Ctrl-[ was more comfortable for me anyway.
(of course that may not work at all in the lambda editor, I'm mostly using it in terminals with heirloom-ex-vi, but seems easy enough to TIAS some time)