{"id":12696,"date":"2025-06-05T15:07:58","date_gmt":"2025-06-05T14:07:58","guid":{"rendered":"https:\/\/www.blopig.com\/blog\/?p=12696"},"modified":"2025-10-03T23:02:36","modified_gmt":"2025-10-03T22:02:36","slug":"on-the-joys-of-vim-like-browsing","status":"publish","type":"post","link":"https:\/\/www.blopig.com\/blog\/2025\/06\/on-the-joys-of-vim-like-browsing\/","title":{"rendered":"On the Joys of vim-like Browsing"},"content":{"rendered":"\n

Reflections on Pointlessness<\/h2>\n\n\n\n

One of the great delights in this life is pointless optimisation. Point-ful optimisation has its place of course; it is right and proper and sensible, and, well, useful, and it also does, when first achieved, yield considerable satisfaction. But I have found I soon adjust to the newly more efficient (and equally drab) normality, and so the spell fades quickly.<\/p>\n\n\n\n

Not so with pointless optimisation. Pointless optimisation, once attained, is a preternaturally persistent source of joy that keeps on giving indefinitely. Particularly if it involves acquiring a skill of some description; if the task optimised is frequent; and if the time so saved could not possibly compensate for the time and effort sunk into the optimisation process. Words cannot convey the triumph<\/em> of completing a common task with hard-earned skill and effortless efficiency, knowing full-well it makes no difference whatsoever in the grand scheme of things.<\/p>\n\n\n\n\n\n\n\n

The technologically-minded, it seems, are afflicted with this irrational mania more often than most. A fair number gleefully shovel hour after hour into such bottomless time-sinks as exotic keyboard layouts; lovingly tended personalised configs; and 200-wpm typing speeds zealously shown off. (Seriously, if you type at 80 wpm, when was the last time you can honestly claim that input speed was the bottleneck to your text or code output?) This is not efficiency; it’s not even procrastination; for many, it is simply a compulsion.<\/p>\n\n\n\n

A time-honoured favourite in this category of ill-advised pastimes is the modal text editor. Not merely being able to use one, no, but peering into its abyssal soul. Grasping at the arcane wisdom veiled within, becoming one<\/em> with the machine. Once truly fathomed, the Zen of vim<\/code><\/a>, it has been said, is no lesser Revelation1<\/a><\/sup> than any Holy Book of scripture yet written. Infinitely more than just an editor, it is a philosophy, a way of life\u2014so I am told.<\/p>\n\n\n\n

Now, ways of life have an unfortunate tendency towards universality. There\u2019s no such thing as a way of life applied to only part of it. It only causes cognitive dissonance, which our species is wont to avoid. Sadly, however, much as the priests of the Creed might want it to, not everything<\/em> can be done in vim<\/code> (I feel the tickling of the pyre-flames already). So what is the aspiring disciple of the Faith to do when they are called upon to leave vim<\/code> behind and venture onto the great wide Web and retrieve some information\u2014or worse, are invited to collaborate in Google Docs or Microsoft Word (\ud83d\ude31, a WYSIWYG-editor? for shame!<\/em>) ?<\/p>\n

Fret ye not, help is at hand! Just because your colleagues have as yet failed to see the Light and subsist on such primitive GUIs and web interfaces as have been handed down from on high, just because you yourself occasionally\u2014unaccountably\u2014succumb to the urge to check a news website or even social media, this does not mean you must spend your life in glacial point-and-click squalor like a cave person. The technological marvels of the age have made it possible to impose the sunlit, Platonic perfection of vim<\/code> onto the shadowy cesspit of the internet; build order from chaos; leave mouse and trackpad behind entirely; tame the unruly seas of information and fly through the ether at lightning (keyboard) speed. We truly live in an age of wonders.<\/p>\n

The key to ennobling your surfing in this way is a vim<\/code>-like browsing extension, as can be procured for every commercially relevant browser including Chrome (and derivatives)<\/a>, Firefox<\/a>, and Safari<\/a>.\nThere is some degree of choice and they differ on the details, but they all provide fully mouse-less web navigation using vim<\/code>-like keybindings (all the more efficient for their vim<\/code>-ness), alongside convenience features like integrated smart search and much besides. Note further that they also constitute a highly effective gateway drug into the Ways of vim<\/code> for your as yet unconverted colleagues; use this information for your proselytising efforts as you see fit.<\/p>\n<\/div>\n\n\n\n

Using a vim Browser Extension<\/h2>\n\n\n\n

I suppose it behooves me to guide the reader through an illustrative example. Here I am (in Chrome, using the Vimium C<\/a> extension) on the front page of a common newspaper whose reporting I occasionally follow. I am interested in the article on medical research funding towards the bottom of the page. How to open it without resorting to the savage ways of the mouse?<\/p>\n<\/div>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Simply type f<\/code> (short for find) or F<\/code> (to open it in a new tab) and every clickable link is highlighted with an easily-typed (case-insensitive) label.<\/p>\n<\/div>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

In this case, type sp<\/code> to proceed to the article. In true vim<\/code> fashion we can now scroll up and down with j<\/code> and k<\/code>, and if the content allows left and right with h<\/code> and l<\/code> (though the arrow keys work as well). We can also page-up and page down with u<\/code> and d<\/code>, jump back to the top with gg<\/code> and to the end with G<\/code>. We can search for the word \u2018health\u2019 with \/health<\/code> (this is smartly case-sensitive) which jumps to the first match and informs us that this word appears 21 times on this page in total. After hitting enter, we can jump from match to match forwards using n<\/code> (next) and backwards using N<\/code>.<\/p>\n<\/div>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

So far so standard, in terms of page navigation; nothing that could not be completed with the built-in (unvim<\/code>like) keybindings (though following specific links would be cumbersome). But there is more. Having now reached the end of the article and being sufficiently horrified about its contents, we wish to return to the newspaper\u2019s landing page. We can certainly just go \u2018back\u2019 in the browsing history by hitting Shift+H<\/code> (and forwards with Shift+L<\/code>), but we can also just gU<\/code> (g<\/em>o U<\/em>p) to the top-most level of the domain. In this case, the article we\u2019re on is at https:\/\/www.nytimes.com\/...\/...\/...\/something.html<\/code> and gU<\/code> lands us back at https:\/\/www.nytimes.com\/<\/code>. We could also gu<\/code> which chops off just the lowermost level of the domain hierarchy from the URL, or 2gu<\/code> for the last two (and so on), though that is only useful on the most hierarchically organised of websites.<\/p>\n

Back on the newspaper\u2019s homepage we hit refresh (r<\/code>), but nothing new comes up. We decide that we will want to come back frequently to keep tabs (heh\u2026) on events, so we bookmark the page\u2014that is, leave a \u2018global mark\u2019 in vim<\/code> parlance. We can pick any capital letter, so let\u2019s pick \u2018N\u2019 (for the NYT) and type mN<\/code> to m<\/em>ark N<\/em>. From now on typing `N<\/code> on any page on the internet jumps back to the NYT homepage. You can also set local marks that only work within<\/em> a page by choosing a lower-case letter (e.g. md<\/code> and `d<\/code> respectively), for example to jump back to an important definition in a long technical blogpost. Marks are overwritten whenever you re-assign a letter in the same context, so you get 26 global marks in total and 26 local marks within any given webpage. That\u2019s plenty.<\/p>\n<\/div>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Leaving aside the NYT we decide we want to look up more information about the NIH, which appeared in the article we just read, on Wikipedia. Type o<\/code> (or capital O<\/code> to do everything in a new tab) to summon the Vomnibar (pictured above). As the name suggests this is a combined URL and search bar (with questionably vim<\/code>-like characteristics), so you can type \u2018wikipedia.com\u2019, if you so choose, or \u2018NIH\u2019 to be directed to your search engine of choice. The Vomnibar also brings up smart suggestions from your recent history and bookmarks below the bar itself, which you can action with Ctrl\/Cmd+1\/2\/3...<\/code>. Most imporantly there are pre-configured options which allow you to search common sites directly without needing to go though a search engine (and you can of course configure your own in the extension\u2019s settings). So, for example, you can search YouTube with yt searchterm<\/code> or in our case Wikipedia with w NIH<\/code> (and then Enter<\/code>), which takes us to the desired page.<\/p>\n

Now Wikipedia in particular has a bad habit of inducing tab proliferation (each opened by capital F<\/code>-ing on a link of interest). Opening a blank tab is naturally just t<\/code>, to move between adjacent tabs use gt<\/code> (g<\/em>o t<\/em>ab forwards) and gT<\/code> (g<\/em>o t<\/em>ab backwards), and to jump to the 5th tab from the beginning try g05<\/code> (for the 5th tab from the end it\u2019s g$5<\/code>). If you\u2019re getting to the stage where you resort to commands like the last one you should consider closing some tabs with x<\/code> for your own sanity. Want to copy (\u2018yank\u2019) the URL of the current page into the system clipboard in order to share it with a friend? Just hit yy<\/code>. Were you just doing that in order to duplicate the current tab? No need, just hit yt<\/code>. Oh, you actually wanted to duplicate the current tab ten<\/em> times? Why that\u2019s just 10yt<\/code>\u2014what exactly are you up to?<\/p>\n

Every once in a while a website will expect input from your keyboard directly. If you want to use an on-site searchbar, for example, are filling out a form, or are using site-specific keyboard shortcuts (hitting f<\/code> on a YouTube video goes f<\/em>ull-screen, for example; hitting \/<\/code> on any Google Search results page focuses the searchbar). In these cases we want our keystrokes to be interpreted by the website, not by the vim<\/code> extension. Is this possible? Of course it is; the extension is based on a modal text editor after all! Just hit i<\/code> first to enter i<\/em>nsert mode, then interact with the website as normal (so that would be if<\/code> on YouTube and i\/<\/code> on Google). Hit Esc<\/code> to get back to vim<\/code> navigation. You can also always hit Esc<\/code> to exit out of a mode you triggered when you did not mean to (e.g. to cancel out of the Vomnibar, or when you hit f<\/code> bringing up link highlights when you meant d<\/code> to go down).<\/p>\n<\/div>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Naturally, as is the way of these things, I have barely scratched the surface of what is possible, and will not go into further detail here. Hitting ?<\/code> brings up a helpful overview for those curious (pictured above). Most importantly\u2014and unlike vim<\/code> itself, whose learning curve is a step function\u2014there is no getting stuck. The extension does not interfere at all with the pre-existing browser keybindings, which you may already be used to and can continue to use if you wish, and if push comes to shove you can always use the mouse (gasp!) if you don\u2019t know what to do. This is perhaps the only example I have found where pointless optimisation is as close to costless as possible, and therefore all the more worthy for those so inclined.<\/p>\n<\/div>\n\n\n\n

To Infinity, and Beyond<\/h2>\n\n\n\n

Speaking of those so inclined, they can of course go further still. There are whole browsers<\/a> written from the ground up with this mode of navigation in mind\u2014sparing space for web content that would otherwise be dedicated to navigation elements.\nFor macOS at least, an app called Homerow<\/a> will produce similar behaviour across the entire operating system, and there will be equivalent applications for Linux and Windows, as well. I leave the exploration of such advanced topics as an exercise for the reader, though whether this is a sensible thing to pursue is another matter.<\/p>\n

In closing, then, let me note only this: No more must you tediously click yourself through system menus! No more must you lift your fingers so much as one inch to reach for the mouse! Cast off the scroll-wheel yoke, comrades, discard the cursor-madness! Let your hearts be free\u2014and fly<\/em>!<\/p>\n<\/div>\n\n\n

  1. My lawyer informs me this is a very dangerous joke to make in this day and age, and tactless besides. \u21a9\ufe0e<\/a><\/li><\/ol>","protected":false},"excerpt":{"rendered":"

    Reflections on Pointlessness One of the great delights in this life is pointless optimisation. Point-ful optimisation has its place of course; it is right and proper and sensible, and, well, useful, and it also does, when first achieved, yield considerable satisfaction. But I have found I soon adjust to the newly more efficient (and equally […]<\/p>\n","protected":false},"author":125,"featured_media":12705,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","wikipediapreview_detectlinks":true,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"ngg_post_thumbnail":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"[{\"id\":\"8ecc5f97-4e44-413e-ad2b-ad511cedc3b0\",\"content\":\"My lawyer informs me this is a very dangerous joke to make in this day and age, and tactless besides.\"}]"},"categories":[296,14,46,586],"tags":[855,332,776,678],"ppma_author":[783],"class_list":["post-12696","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hints-and-tips","category-howto","category-humour","category-os","tag-browsing","tag-humour","tag-software","tag-vim"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.blopig.com\/blog\/wp-content\/uploads\/2025\/06\/1538224B-E069-4D8F-A912-0E93E457D376.png?fit=1536%2C1024&ssl=1","jetpack_sharing_enabled":true,"authors":[{"term_id":783,"user_id":125,"is_guest":0,"slug":"ody","display_name":"Odysseas Vavourakis","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/b74030bdaef5f39ec32be3ae7bb5af054cbcb0b431b1cc51ba1b41d723ecee48?s=96&d=mm&r=g","0":null,"1":"","2":"","3":"","4":"","5":"","6":"","7":"","8":""}],"_links":{"self":[{"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/posts\/12696","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/users\/125"}],"replies":[{"embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/comments?post=12696"}],"version-history":[{"count":5,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/posts\/12696\/revisions"}],"predecessor-version":[{"id":12720,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/posts\/12696\/revisions\/12720"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/media\/12705"}],"wp:attachment":[{"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/media?parent=12696"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/categories?post=12696"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/tags?post=12696"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.blopig.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=12696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}