Surfingkeys VS vim-easymotion

For the privacy-conscious interested in SK, it may be worth a read of this GH issue: https://github.com/brookhong/Surfingkeys/issues/1796

I empathise with the author wanting to make a buck but it's hard to reconcile the approach he took with the level of trust granted to this extension.

Hope this helps someone looking for a better option migrating from Vimium.

[0] https://github.com/brookhong/Surfingkeys

Was this issue about the bundled search hijacker resolved in some sort of positive way? I abandoned SurfingKeys as soon as I heard about that and haven't looked at it again. It'd be nice if that was all rolled back, but I switched to Vimium and haven't found it to be particularly worse, at least not for the way that I browse the web. The only thing that I've been missing is the vim-like text editor but, for me, that's a relatively minor feature; I don't write giant comments that often.

Look into surfingkeys

Moved from it in favor of more features that surfingkeys provide. If you know a little bit of javascript you can conquer your browser!

Tridactyl's key feature is "native messaging".

A further alternative is https://github.com/brookhong/Surfingkeys. Its key feature is a javascript configuration - allowing you to bind arbitrary javascript to a key.

I can highly recommend this extension. It looks similar to the one you use.

Manifest V2 deprecation is likely going to break extensions that inject userscripts, like Tampermonkey [0] and SurfingKeys [1]. The Chrome team has been rather unhelpful. They've promised to add support for power-user tools like these in MV3:

dotproto from the Chrome team commented on May 27 [2]:

> @mon-jai, the short answer is no, I don't have any updates to share. That said, I'll reaffirm that we plan to support userscript managers in Maniest V3 before the Manifest V2 deprecation.

But the deprecation is approaching and the Chrome team hasn't released any more information about this AFAIK. These extensions are going to require large refactors to support MV3 and they can't meaningfully start until the Chrome team elucidates how script injection will work. With MV2 deprecation coming so soon, I worry there won't be enough time.

[0]: Manifest V3: examine the effects · Issue #644 · Tampermonkey/tampermonkey: https://github.com/Tampermonkey/tampermonkey/issues/644

[1]: Migrate to Manifest V3 · Issue #1821 · brookhong/Surfingkeys - https://github.com/brookhong/Surfingkeys/issues/1821

[2]: https://github.com/Tampermonkey/tampermonkey/issues/644#issu...

Why not sneak or easymotion?

I'm also on team no remap. I don't use hjkl anymore and instead have a nav layer bound to where hjkl would be when I hold a thumb key down. I also use https://github.com/easymotion/vim-easymotion Bound to norm s.

Incredible that nobody mentioned vim-easymotion - totally necessary for me.

But have you tried https://github.com/easymotion/vim-easymotion (I recommend let mapleader = "\").

By vim motions, do you mean native motions or extended motions with plugins like vim easymotion and vim sneak? Those are the two I've been trying out recently.

Been around since ~2012 via vim-easymotion as well: https://github.com/easymotion/vim-easymotion

I second the suggestion of using a plugin like easymotion. https://github.com/easymotion/vim-easymotion

For switching: I suggest you try easymotion. Basically it lets you jump (or I'd like to call it teleport) to anywhere on screen even across visible windows. I cannot imagine my workflow without it.