dotfiles VS Surfingkeys

I forgot to mention that I use a compositor (picom) to fix screen tearing with this config: https://github.com/MarcoLucidi01/dotfiles/blob/master/.config/picom.conf

I love it! I'm so used to it that using a browser without it it's (almost) like using an editor that's not vim! here there are my mappings if you want to try them out, the one I use more often are:

buffers and splits for managing multiple opened files, this stackoverflow answer helped me understanding the difference between buffers and tabs in vim (I never use tabs). I have this gem in my vimrc:

I don't mind posting it, but be aware it's not an Obsidian script, I use from the browser, using it from an extension called SurfingKeys

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.

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.

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.