Geek with an attitude

A little over 6 years ago, or just 2 posts below :), I wrote about how I use VIM from the command-line to invoke a GUI version of VIM, where each file would appear in a separate tab. I've stuck with that setup to this day, where VIM is still my main IDE whether working on Linux or macOS. Recently I bought a pine64 based PINEBOOK Pro  laptop which is powered by a low-cost ARM64 Single Board Computer (SBC) . This came pre-installed with Manjaro KDE edition of Linux. Though this laptop is no slouch (I find myself using it more thanks to 8hrs+ battery), I wanted to keep it lean without loading too many GTK apps. KDE, being built on Qt, I decided to try neovim-Qt, which is powered by neovim, a somewhat newer rewrite of VIM, that is pretty slick and fast. This is how I got neovim-Qt working in a similar manner to that of vim / gvim. Install packages First, install neovim-qt. On Manjaro, this would involve pacman. sudo pacman -Sy neovim-qt Next, the secret sa...

It’s been a really really long time since I last blogged so bear with me while I try get a little bit of my mojo back :) I’ve been busy changing countries, cities, apartments, jobs – the usual stuff life throws at you. But the one thing I’ve tried to change and keep coming back to is my beloved editor – VIM. This post is on making VIM a little better, like that other one developers tend to use these days. Don’t get me wrong, I’m not suggesting VIM is better (or worse). But after having used VIM for so long, I don’t want to just give up on it. If you’re in the same camp then read on. Get me some of that WYSIWYG I know what you’re thinking – VIM is awesome because its all terminal. And there is no reason to give that up! I haven’t, especially for those quick edits. However when it comes to coding for any length of time, my goto editor has been one where VIM is wrapped in WYSIWYG goodness. I’m talking about the likes of gVim alternatives such as vim-gnome (Linux Gnome...