What does HackerNews think of 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.

Language: JavaScript

#50 in JavaScript
Show HN: Using Vim as an input method editor (IME) for X11 apps | Dec 2022
On OSX w/ Chrome I use wasavi[0], an extension that implements a nice subset of vim directly in the text area (much like OP's system, but not using actual vim). Works really well, better than other extensions I've tried that attempt to ~shellout to $EDITOR and then sync back to the input area.

[0] https://github.com/akahuku/wasavi

Why Should You Learn Vim in 2020 | Aug 2020
Expand Context ↕
I read this comment 20 minutes ago and tweeted about it. I came back here to provide a link to a browser plugin for vi keybindings and found many other people had also commented with examples- only different ones.

Here’s another:

https://github.com/akahuku/wasavi
Big Pile of Vim-Like | Dec 2019
I can recommend Wasavi, which is a browser extension that allows you to use Vim commands in most text windows you can edit. https://github.com/akahuku/wasavi I use it on a daily basis and although it's not Vim it's still pretty good.
Vim Anti-Patterns (2012) | Mar 2019
Expand Context ↕
If you just want a vi/vim toggle for your browser, wasavi[1] is what you're after.

https://github.com/akahuku/wasavi
Linux Desktop Setup | Feb 2019
Expand Context ↕
Wasavi does exactly what you want:

http://appsweets.net/wasavi/

https://github.com/akahuku/wasavi
NeoVim 0.2.0 released | May 2017
Expand Context ↕
You might like this -

https://github.com/akahuku/wasavi

I'm hoping it's ported to Firefox when webextensions are ready.
Azure Jupyter Notebooks | Dec 2016
Expand Context ↕
I use wasavi, https://github.com/akahuku/wasavi, which does exactly what you describe.
Advanced Deanonymization Attacks | Aug 2016
Expand Context ↕
Reading your comment and looking at the proposed solutions, it made me think of an interesting browser plugin, and wonder how it could affect this issue, or if it could even potentially solve it to a certain degree.

Wasavi. It's a plugin to emulate a small vim-like window on top of text-fields. You just Ctrl+Enter and it opens up, and when you save it (like vim with :wq or ZZ) it populates the field beneath it. It's quite interesting. I wonder if taking this approach to the extreme wouldn't make a difference? If all text fields were abstracted from the website and then the text sent in one stream, for all users.

I unfortunately do not possess the knowledge to understand if this is plausible or absurd, but wanted to at least discuss it publicly.

Edit: Wasavi on Github: https://github.com/akahuku/wasavi

This behavior does also exist for those accustomed to Vimperator, Pentadactyl or It's All Text plugins, but opening your default editor outside of the browser.

Edit 2: Wasavi supports many text input fields (including passwords), and can be configured to be enabled automatically on field focus.