Vimconf 2021 – Oct 29, 30
vimconf.live
vimconf.live
I'm looking at you GtkFileChooser (or almost any GUI file browser for that matter)
Hopefully other applications will pick up more of these over time
Highly recommended.
If I were to give a talk, I would do it on qutebrowser.
If you like using Vimium, you owe yourself to try out qb, where keyboard gets first class in the application, not second-class injected into some pages with JS.
No need to contribute to the Chromium monopoly, luakit (what this comment’s sent from) and some other browsers (off the top of my head: nyxt and, to varying extents, Palemoon, lynx, and eww + evil-mode) offer the same thing.
All the keyboard shortcut always work, not just once a tab that's allow-listed has been loaded and JS has been injected into it.
All the settings, including e.g. tab position, fonts, tab loading indicator colors, etc. are configurable via :set
All keys are bindable to all commands via :bind
JavaScript, image loading, etc can be toggled globally, per domain, or for individual pages with keyboard shortcut.
Also, there is an amazing support channel on IRC.
I sympathize with your dislike of the Chrome monopoly. I test my websites in Lynx, Links, AND w3m, not to mention Netscape, IE, Opera, Firefox, PaleMoon, Waterfox, Safari, and many others. However, I also want a usable and performant browsing experience -- something Chrome definitely does not provide, but qb does. I don't think it's anywhere close to being Chrome, it is way better.
Anything Chromium based is virtually as bad as Chrome in terms of increasing the engine’s market share, making it the de facto standard and making the majority of web devs test their sites less or not at all on other engines (I appreciate you being an exceptional dev in that regard, but I’d appreciate more you doing your small part to influence all the other devs of the sites you use).
(Not to mention that installing evil in vanilla Emacs requires too much hassle, including first manually adding melpa as a package repo — which drove me to spend a lot of time trying to make do with viper mode — and later choosing yet another package to be able to redo, unless you use the unreleased Emacs 28. That pain is probably my fault for giving up on Doom because its support chat requires a nonfree client, and for not trying spacemacs yet.)
If it’s a simple replace symbol, its easier to do it with rg -l and sed -i, of course.
On occasions when I’m doing things more iteratively (because I’m using a few macros and personal judgement), I commonly end up with :wn<Enter> in one of the macros.
> Kakoune’s grammar is object followed by verb, combined with instantaneous feedback [in vim, it’s verb followed by object]
> vi treats moving around and selecting an object as two different things. Kakoune unifies that, moving is selecting. w does not just go to the next word, it selects from current position to the next word
(source: http://kakoune.org/why-kakoune/why-kakoune.html )
The increased interactivity seems nice but the loss of backwards compatibility and having to relearn and retrain basic commands seems not worth it to me.
And, if a feature is desirable enough, I know it’ll end up as a vim feature sooner or later. Like JSONB, timescaledb, etc. for PG.
Kakoune looks like it has some cool features! They’ll probably end up in Vim (or nvim) eventually.