Vim on mm-dev

Set up Vim for Flutter

Thu, 08 Aug 2024 17:47:33 +0100

There are various ways of installing Vim plugins. I use vim-plug in my examples here but I’ll add links to instructions for each plugin so you can do it your own way.

Dart

As Flutter uses the Dart language, install Dart support for Vim. I add the following to my ~/.vimrc:

" Between the 'plug#begin()' and 'plug#end()' lines
Plug 'dart-lang/dart-vim-plugin'

Then I restart Vim and run :PlugInstall.

This adds syntax highlighting and auto-indentation of Dart code.

Language Servers

Language Servers/LSPs (LSP = Language Server Protocol but both terms are often used interchangeably) give your editor information about the structure of a language and enable it to do syntax highlighting and code completion, along with deeper functionality such as allowing you to jump to the definition of a function, do refactoring etc.

LSPs are used in Visual Studio for a lot of its advanced functionality but they can also be used in Vim. There’s more than one way of doing this but I use coc-nvim (despite the name it works in modern versions of Vim, not just Neovim).

Install the `coc.nvim` plugin in Vim

Using vim-plug I add the following to my ~/.vimrc:

" Between the 'plug#begin()' and 'plug#end()' lines
Plug 'neoclide/coc.nvim', {'branch': 'release'}

Again, I restart Vim and run :PlugInstall.

For other ways of installing just follow the instructions .

Install a Flutter LSP

Install the Flutter language server in CoC, coc-flutter. This provides lots of helpful functionality for working with Flutter in Vim as described in the link.

:CocInstall coc-flutter

This LSP needs to know where the Flutter SDK is installed. In Vim, run :CocList FlutterSDKs and make sure it finds at least 1 SDK. If not, add a line to CoC settings (:CocConfig):

"flutter.sdk.path": "$HOME/.local/flutter/bin"

You can find the correct path with which flutter in the terminal.
Originally, I had installed my Flutter SDK at /usr/bin. That caused invisible errors with coc-flutter as it couldn’t access the path properly to find the Flutter SDK. I was having trouble getting this step working. I then moved the Flutter SDK to $HOME/.local/flutter and everything started to work properly

`coc.nvim` settings

To change CoC settings the command :CocConfig can be used in Vim. On my system it opens up the file ~/.vim/coc-settings.json. You can open/edit this file directly but depending on your Vim configuration it may be in a different location.

Here are some of the settings I prefer:

{
  "diagnostic.checkCurrentLine": true,
  "diagnostic.enableMessage": "jump",
  "colors.enable": true,
  "suggest.noselect": true,
  "inlayHint": false
}

`"diagnostic.checkCurrentLine": true,`

By default, Coc will show you a diagnostic error or warning when your cursor is over the word causing the problem. Setting this to true means you only have to be on the same line as the error to see the dialog, not the exact word.

`"diagnostic.enableMessage": "jump",`

This diagnostic popups can be really helpful, but it’s all a bit frenetic for me, I’m a prefers-reduced-motion kind of person. Setting this to jump means they don’t pop up automatically, but can still be shown when I want to see them. I also add this line to ~/.vimrc:

nmap <silent> gh <Plug>(coc-float-hide)
nmap <silent> gl <Plug>(coc-diagnostic-info)

Which allows me to show/hide the diagnostics with gh/gl respectively.

`"colors.enable": true,`

This setting is for another CoC addition called coc-highlight. I installed this in Vim with:

:CocInstall coc-highlight

This adds various types of colour highlighting, but the one I was most interested in is how it will detect any colours (eg RGB or hex) in your code and change the colour of their text to give you a preview of them. This feature is enabled with the colors.enable line as above.

`"suggest.noselect": true,`

When you start typing a word, CoC will default to inserting its first suggested autocompletion word. This is a bit more ‘help’ than I like, so I add this setting to make the process more intentional.

`"inlayHint": false,`

By default CoC inserts inlay hints, for example if you haven’t added a type hint to indicate what kind of widget is being referred to somewhere, it will insert the <Widget> hint for you as a piece of magical ghost text.

These bizarre bits of text appear in the middle of lines of code, except they aren’t really there, you can’t select them or delete them and if you’re moving your cursor around it acts as if they don’t exist. I’m sure some people enjoy them, and for those people I’m glad that they exist. For me, they are disgusting, obnoxious devil-warts.

Thankfully, they can be vanquished by adding this line to the CoC settings.

Install Flutter

Thu, 08 Aug 2024 17:47:32 +0100

Follow instructions from https://docs.flutter.dev/get-started/install/linux/android

Download the flutter_*.tar.xz archive
Unpack the archive into $HOME/.local/bin (creates $HOME/.local/bin/flutter/bin)
At first I tried putting this at /usr/bin, but that caused invisible errors in coc-flutter as it couldn’t access the path properly to find the Flutter SDK
Add the new path as above to $PATH eg in ~/.profile

# ~/.profile
export PATH="$HOME/.local/bin/flutter/bin:$PATH"

For ARM64 architectures the Flutter SDK cannot be found at the above link, nor in the archives. In this case the SDK can be obtained by cloning the main flutter repo, then running a flutter command to trigger a download of dependencies
git clone -b main https://github.com/flutter/flutter.git
./flutter/bin/flutter --version

Agree to more licenses and get Flutter doctor to pass

First, agree to several laughably long licence agreements which Google knows full well that nobody reads.

flutter doctor --android-licenses

Then type Y and Enter for each prompt

Now run flutter doctor. It should pass every test except ‘Android Studio (not installed)’. If so, we’re ready to start building Flutter apps (with Android Studio not installed).

Sample project

You can make a really simple sample project to check that everything’s installed correctly and see how it works.

flutter create sample-project

This will create a sample-project directory with a Flutter app in it, a simple built-in demo of a button which counts up as you tap it.

To run the app:

cd sample_project
flutter run

Install the Android SDK

Thu, 08 Aug 2024 17:47:31 +0100

Getting the Android SDK set up manually can be tricky, I think the expectation is that most people will use Android Studio so not a lot of work has been put in to making manual installation user-friendly.

Pick a directory where you’ll keep the SDK

This is an important directory that will always store all the Android-SDK specific tools, platforms, build tools etc. Various bits and pieces need to know where these things are, so we’ll set some environment variables for them later.

I’m using $HOME/android_sdk/ in these examples.

mkdir $HOME/android_sdk

Install the SDK Manager

This is a set of command line tools used to install different versions of the SDK (for when you want to target different Android devices).

Based on Google’s instructions at https://developer.android.com/tools/sdkmanager.

From the downloads page (I had to scroll down a long way), download the cmdline-tools zip and unzip it to the directory you created above eg $HOME/android_sdk/
Inside the unzipped directory cmdline-tools make a ’latest’ directory and move all of the other contents of ‘cmdline-tools’ inside it (so you end up with cmdline-tools/latest/bin

You should end up with something like the following (I’m using tree to list the directory contents but don’t worry about that, just make sure your directories are in the right places):

$ tree -L 2 cmdline-tools/
cmdline-tools/
└── latest
    ├── NOTICE.txt
    ├── bin
    ├── lib
    └── source.properties

Add some environment variables to `~/.profile`

Make sure these make sense based on what we’ve done so far if you’ve used different directories to me.

# ~/.profile
export ANDROID_SDK_ROOT=$HOME/android_sdk
export PATH=$PATH:$ANDROID_SDK_ROOT/cmdline-tools/latest/bin
export PATH=$PATH:$ANDROID_SDK_ROOT/platform-tools

Source the profile with source ~/.profile. Then run sdkmanager and see if it does something. If you get command not found double-check everything and try rebooting.

My sdkmanager binary name clash (this won’t affect you but click to expand if you’re interested)

In my case I already had a binary installed with the name sdkmanager, as that’s the name Garmin use for their ConnectIQ SDK Manager. Apparently neither Garmin nor Google could foresee that anyone other than themselves might call their SDK manager software ‘sdkmanager’.

So I had to do some hacky stuff with bash aliases in ~/.profile to let the two live alongside each other, and remind me of the situation:

alias sdkmanager='echo "Use either *sdkmanager-garmin* or *sdkmanager-android*"'
alias sdkmanager-android=$ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager
alias sdkmanager-garmin=$HOME/.local/bin/sdkmanager

Accept SDK licences

The SDK licences must be accepted for everything to work.

sdkmanager --licenses

Then type Y and press Enter for each prompt

Install the Android toolchain

To pass the ‘Android toolchain’ step of flutter doctor (in a bit) we need 3 things:

Platform tools (generic)
A valid platform
Build tools to match the platform

Various instructions online will tell you to do things like sdkmanager "platform-tools" "platforms;android-33" (ie pass multiple arguments to sdkmanager), but as observed in this StackOverflow answer if using the command line tools, the platform tools need to be installed via separate commands ie:

sdkmanager 'platform-tools'
sdkmanager 'platforms;android-33'
sdkmanager 'build-tools;33.0.2'

If the installation has worked correctly you should end up with something like:

$ tree -L 1 android_sdk/
android_sdk/
├── build-tools
├── cmdline-tools
├── licenses
├── platform-tools
└── platforms

Another weird, me-specific problem I encountered…

At first, my installations weren’t appearing in my android_sdk directory and Flutter tools were complaining about not being able to find the Android SDK.

Forcing the SDK path like this worked: sdkmanager --verbose "platform-tools" --sdk_root=$HOME/android_sdk/

But something smelt wrong, as the original sdkmanager install commands seemed to be completing without error. I investigated this by running the following:

sdkmanager 'platform-tools' --verbose

Which revealed that they were going into:

/data/data/com.termux/files/usr/share/android-sdk/

This is because I was on Android using Termux, in a proot container, and I had previously installed the SDK in the main (non proot) Termux environment. This was not needed any more so I deleted the other installation.

This is an exotic situation and you’re probably not as stupid as I am to get into this situation, but maybe this note will help in some other situation.

Dependencies and Environment

Thu, 08 Aug 2024 17:47:30 +0100

To get started I’m presuming you have a Linux installation of something like Debian/Ubuntu.

General Dependencies

Git

You probably already have this but just in case:

sudo apt install git

Ensure Java JDK is installed and recent enough

sudo apt install openjdk-17-jdk

Stuff Flutter Needs

The latest info about this should be here but at time of writing:

sudo apt-get install -y curl git unzip xz-utils zip libglu1-mesa

And some other tools Flutter uses:

sudo apt install clang cmake ninja-build

If using Chromium browser instead of Chrome

The Android SDK likes to know where Chrome is on your system. I use Chromium and the SDK can’t find it.

So I export an environment variable to let Flutter know where to find Chromium eg in ~/.profile

export CHROME_EXECUTABLE=/usr/bin/chromium

Parts of the SDK

Thu, 08 Aug 2024 17:47:30 +0100

There are several components making up the SDK. I’ll list them here along with examples of how they can be installed later on when the SDK manager is set up and working.

This is just an overview to help your mental model of what’s what, we’re not installing anything just yet.

We download them as a zip and place them in a specific directory, as detailed later.

Command Line Tools

These commands can do several things like signing and optimising APKs, but the main one we are interested in is sdkmanager. This is the command we use to install the other tools.

Platform Tools

These are tools for interfacing with Android which you may already be familiar with, such as adb and fastboot.

sdkmanager 'platform-tools'

Platforms

A platform represents a specific version of Android. It includes multiple system images, which the device emulator uses to emulate various devices on that platform.

Information used to compile your app for this platform version, and source code to be used for debugging are also included.

Multiple platforms can be installed alongside each other on the same system.

sdkmanager 'platforms;android-33'

Build Tools

These are tools used for building Android apps. I’m not 100% clear on what these are and why they are different from Platform Tools, it seems that they were part of Platform Tools in the past but have been sectioned off into their own thing.

Anyway, we need them. Usually use the latest version, but sometimes if you’re targeting specific platforms eg older ones, errors may indicate that you need an older version.

sdkmanager 'build-tools;33.0.2'

Intro

Thu, 08 Aug 2024 17:47:29 +0100

Given the choice, I’d rather avoid huge complex apps like Android Studio. They use a lot of system resources and are very GUI/point-and-clicky. Those things definitely have their place but I prefer keyboard control where it makes sense, and for me programming in Flutter is one of those situations.

A lot of what Android Studio does behind the scenes is automatically editing text files and running shell commands such as flutter run, flutter build and so on. If you’re comfortable with the terminal these commands are fairly simple to run manually.

As an IDE Android Studio also helps with stuff like syntax highlighting, code completion, refactoring etc. If you’re into Vim it can be set up to give you these pleasantries. I’m sure there is stuff Android Studio can do that Vim can’t, but whatever it is I’m not missing it and I feel good when I use Vim.

I’ve set up a couple of systems with this Flutter dev environment recently and hit some stumbling blocks. They weren’t too hard to resolve but I wanted to write up the process for future reference and to help anybody else in a similar situation.

Vanilla JS

Fri, 05 Apr 2024 12:18:03 +0100

Toolchain

I enjoy using plain/vanilla JS where possible. For my own projects I try to avoid the sprawl and long build times of NPM.

I do like to split my code up into separate modules though, and to be able to benefit from bundling/minification etc, for which I use esbuild. I also want to be able to use SCSS and JSDoc for type annotations. So I do allow myself some minimal tooling (the cone and Flake).

My setup looks like this…

esbuild - Download a build

JS bundler
Combine separate modules into a single JS file, minifying/compressing if required
Tree shaker
Avoid bloat by making sure only those modules/functions which are used get added

I use esbuild for most JS projects, so I installed a standalone build which can be run from anywhere — but it can also be installed using npm or other methods.

SASS - How to Install SASS

Compiler and bundler
Converts SASS/SCSS files into CSS

JSDoc - Documentation

Automated documentation creation
HTML docs for your methods, classes and variables will be created based on your code comments
Type annotations
Comments in your code can tell JSDoc which data types your code expects

Type annotations you provide (in specially-formatted comments) will be used to automatically create detailed documentation for your project.

Docs are created as HTML files, with lots of clickable cross-references. The files can be styled based on a templating system and CSS styling.

Lots of modern editors/IDEs will also use your type annotations to provide type hints and draw attention to potential problems eg if you try to pass an argument of the wrong type you’ll get a warning.

Example of Project Setup Using Tmux/Vim

I usually write a simple bash script for most projects. I’ll run this script when I want to start a session of working on a specific project.

Below is an example build script (for my ‘Pipe Dream’ game) which does the following:

Enters the project directory
Uses tmux to open a few window panes/splits:
- esbuild watching for changes to JS
- SASS watching for changes to CSS
- JSDoc watching the src directory (in reality I’d often skip this and run it manually on-demand, as it can be slow)
- git status, pane left open for commits etc
- A simple Python server so I can test the app in a browser
Opens a vim session with the relevant source files ready for editing

#!/bin/bash

# Open a JS project using esbuild, SASS and vim

work_dir="$HOME"/pipe-dream/

'tmux' \
    new-window -c "$work_dir" "esbuild src/main.js --outfile=www/js/pipe-dream.js --target=es6 --bundle --minify --sourcemap --global-name=PIPEDREAM --format=iife --watch" \; \
    split-window -c "$work_dir" "sass --watch src/scss/:www/css/" \; \
    split-window -c "$work_dir" "jsdoc src/ -c jsdoc.config" \; \
    split-window -c "$work_dir" "git status; bash -i" \; \
    split-window -c "$work_dir" "python -m http.server --directory www/" \; \
    select-layout even-vertical \; \
    new-window -c "$work_dir" "vim -S vim.Session" \; \

Vim Configuration

I’m one of those Vim people. People say its codebase is bloated but in use it always feels crisp and fast to me. Because of the way you manipulate text objects and leap around the page it somehow feels efficient on low-powered/slow devices, and works particularly well with e-ink devices.

Some people argue that they’re faster while using Vim than they are in other code editors. I’m not sure if I’m faster (I might be), but I’m from the school of thought that if your bottleneck when writing code is your typing speed, that might not be a good thing.

More importantly for me, I like the way Vim makes you think about text, as beautifully described in this classic stackoverflow answer ‘Your problem with Vim is that you don’t grok vi’.

I don’t like my coding environment to be too noisy or intrusive, but there are some powerful IDE features available nowadays and I don’t want to cut off my nose to spite my face.

Below is some info on some Vim plugins I use to help with JS development.

coc-nvim - Code of Conquer project repo

Although the ’nvim’ stands for Neovim (the popular Vim fork), COC also works very well in modern versions of normal Vim. This plugin allows VSCode-type IDE features, being based on the Language Server Protocol standard.

Very simply, a language server is a tool which understands a specific language, and can be used by your editor/IDE to analyse and give feedback on your code as you write it. It can do things like:

Syntax highlighting
Code completion
Draw attention to errors and give warnings about code
Help when refactoring code

COC isn’t a language server itself but it allows you to install and maintain whichever servers you need for the languages you use.

For example the language server I use for JS is coc-tsserver. The ’ts’ stands for TypeScript but it works very well with standard JS too. Along with the benefits mentioned above, this language server allows you to use type-checking, like TypeScript but without the compilation step. It also provides documentation and hints on using standard built-in JS methods.

You annotate your code by providing special comments in JSDoc syntax. When these comments/annotations are present, COC and the language server give you lots of hints while writing code, and warn you if you try to provide arguments of the wrong type.

Here is an example (from the official docs) showing what the JSDoc syntax looks like:

/** Class representing a point. */
class Point {
    /**
     * Create a point.
     * @param {number} x - The x value.
     * @param {number} y - The y value.
     */
    constructor(x, y) {
        // ...
    }

    /**
     * Get the x value.
     * @return {number} The x value.
     */
    getX() {
        // ...
    }

    /**
     * Get the y value.
     * @return {number} The y value.
     */
    getY() {
        // ...
    }

    /**
     * Convert a string containing two comma-separated numbers into a point.
     * @param {string} str - The string containing two comma-separated numbers.
     * @return {Point} A Point object.
     */
    static fromString(str) {
        // ...
    }
}

Sometimes the help is a little noisy though…

I love the functionality, but for me it’s a bit over-eager, eg if I’m half-way through typing a word I don’t need a popup telling me the word doesn’t exist.

coc-nvim does also provide a small symbol at the start of each line where it detects an error or wants to warn about something. So I like to leave the symbol visible, but hide the info popups by default. I add a keyboard shortcut so I can show/hide the explanation of the error/warning when I want to.

To stop the popups:

// In ~/.vim/coc-settings.json

{
  ...
  "diagnostic.enableMessage": "jump",
  ...
}

To add the show/hide keyboard shortcuts to Vim:

" In ~/.vimrc

nmap <silent> gh <Plug>(coc-float-hide)
nmap <silent> gl <Plug>(coc-diagnostic-info)

Prettier

This opinionated code formatter formats your code according to some fairly strict rules and has few configurable options (ie it’s their way or the highway).

I think most people find at least some of the rules disagreeable, but the point of this kind of tool is that it does a ‘decent, not perfect’ job, but provides a standard for formatting and removes the need for discussing, disagreement and wasted time.

I found it a little annoying at first but then got over myself and prefer now to use it whenever possible.

The Bad Parts

Fri, 05 Apr 2024 11:44:43 +0100

The Low Memory Killer Daemon - Official Docs.

This feature of modern Android versions kills tasks (/apps) when it thinks they are causing memory-related performance problems. It can feel pretty heavy-handed, with apps abruptly closing at seemingly random intervals.

In practice this can irritate but I’ve never lost any work because of it. The most noticeable occurrence is when Termux:X11 closes — my Linux desktop suddenly shuts down! Sounds terrible But actually my Vim buffers are constantly auto-saved, my browser tabs are stored… I just have to restart the session, then Tmux, then maybe a couple of other items. I’m back up and running in 1-2 minutes, and this problem might occur once or twice per week at the most.

There are various ways to tweak the daemon though, search for terms like ‘disable android oom killer’, ’tweak low memory killer daemon android’ etc.

Missing Tools for ARM Architecture

As the types of CPU in Android devices (usually ARM) are not the same as those used in laptops/desktops (usually X86), the standard desktop versions of software can’t be installed and compatible versions must be available (unless you want to compile them yourself).

This isn’t as bad as it sounds as the package manager for whichever distro you use will automatically pull in the correct version for your CPU architecture. Some software might be missing though.

A couple of specific gaps in the system affect me:

Garmin Monkey C
Garmin apps are written in their own language ‘Monkey C’, which has to use their own Java-based compiler and device simulator. As far as I can tell this isn’t happening on ARM. It was hard enough to get it working on Linux and Vim as they presume Windows/VSCode in their tutorials, so once I achieved that I didn’t take it any further.
Flutter cross-compilation
The situation with Flutter is strange. Flutter is used to make multi-platform apps, so the same code can output apps for Linux, Android, Windows etc. I can build a Linux (ARM64) binary on my Android Ubuntu… and I can build an Android binary on my (normal, X86 desktop) Linux. But I can’t build an Android binary from Android. Apparently people were able to do this on older versions of Flutter, so it seems like Google (who control Flutter) intentionally stopped supporting it.

Fingers crossed!

Mine is a niche use-case and I understand that I can’t expect organisations to support such a tiny minority as ARM Linux. Apple’s M1/M2/M3 ARM chips are doing very well, which is great if you’re into that but I don’t enjoy their ecosystem.

So for now I need to hang on to my X86 desktop. But I hope ARM continues to gain recognition as more than a mobile phone CPU and can be used for more development tasks in future.

Software

Fri, 05 Apr 2024 11:44:41 +0100

Although this is all in relation to working on Android, the software I use is generally the same as if I was on a Linux desktop. That’s kind of the point, nowadays I can use almost the same environment on Android as I can on my desktop.

Termux

Termux is a brilliant free terminal app and Linux environment for Android. It has most of the Linux commands I need and I can install git, Vim, Tmux, mutt, ImageMagick and the majority of the terminal software I like to use. For certain jobs such as scripting, SSH sessions and writing, this is all I need.

Termux can run non-terminal, graphical apps too, but you won’t be able to see them. That’s what the next app is for.

Termux:X11

This amazingly useful app describes itself as being in early development, but I’ve been daily-driving it for months without significant issues.

Termux:X11 is an X Server for Termux. This allows you to install graphical Linux apps, as long as they are available for your system architecture (ie AArch64 — or ARM64 as it’s known — for most modern Android devices).

This means I can run, directly on my tablet:

Desktop Firefox (so, full developer tools)
Desktop Chromium (this was quite hard to get installed and isn’t the absolute latest version but is still very useful for development)
Krita/Inkscape/GIMP for image processing
Thunar file manager
Audacity (using PulseAudio over the network to pipe the audio up to Android by using the devices own IP address… I’m sure this creates some delay/latency but I’ve not noticed it in practice and for my typical usage of minor adjustments to audio files it works well)

PRoot Distro

This is a ‘container environment manager’ and allows you to easily install, uninstall, backup and restore Linux distributions, alongside/on-top-of Android, sharing the kernel.

It’s really simple to use, eg installing Debian Linux is a matter of opening Termux and entering:

proot-distro install debian

Then for a shell login:

proot-distro login debian

PRoot Distro provides a nice choice of distros including:

Alpine Linux (edge)
Arch Linux ARM
Artix Linux (AArch64 only)
Debian (stable)
Fedora 38 (AArch64 only)
Manjaro (AArch64 only)
OpenSUSE (Tumbleweed)
Pardus (yirmibir)
Ubuntu (23.10)
Void Linux

You can install as many distros as you want and swap between them easily. Each distro just sits in a directory on the Android device. Using the backup tools the entire system can be bundled up as a single archive file and moved over to another Android device.

Window Management

I believe that the best user interface (actually, interface of any kind) is one that I don’t even notice exists. It doesn’t shout at me, it doesn’t wow me with animations and eye-candy. It allows me to get to the tools I need to get the job done and stay immersed in the task. It is at peace with itself enough to take a back seat and not demand attention. It is, conceptually, transparent.

A lot of people like the gestural UI featured in ‘Minority Report’. I like the film, and the scene with Tom Cruise manipulating the UI is well produced and fun to watch. But as a UI it’s terrible! Hugely inefficient with all those big sweeping hand gestures, it’s not quick or practical. I don’t want to have to perform interpretive dance to use my computer (nor watch my computer doing little performances when I’m trying to get stuff done).

I found similar sentiment in this Daring Fireball article about the Apple Vision Pro:

“To me the Macintosh has always felt more like a place than a thing. Not a place I go physically, but a place my mind goes intellectually. When I’m working or playing and in the flow, it has always felt like MacOS is where I am. I’m in the Mac.

“Interruptions — say, the doorbell or my phone ringing — are momentarily disorienting when I’m in the flow on the Mac, because I’m pulled out of that world and into the physical one.”

I am nearly exactly like this too, except I don’t want to feel like I’m “in the Linux” (and definitely not “in the Mac” or “in Windows”!). I don’t want to be aware of that layer of abstraction at all. I don’t mind feeling that I’m “in Vim”, but really I want to be “in the code” that I’m editing. I specifically don’t want to feel the manicured claw of a corporate behemoth like Apple or Microsoft on my shoulder… but that’s just me.

I’d rather forget that my OS(/window manager) exists. It’s a facilitator, not an end in itself.

DWM: Tiling Window Manager

I used to prefer larger screens and multiple monitors. I knew about the concept of workspaces but they sounded annoying and fiddly. It took me a long time to give them a chance and it happened accidentally, as a side-effect of trying a tiling window manager.

Very briefly, a tiling window manager organises your windows into tiles, meaning instead of having oddly-sized overlapping windows floating around making a confusing mess of your screen and using space inefficiently, your screen splits into fractions, each being filled by an app. If you have too many apps on the screen they can go onto other screens, or ‘workspaces’. Personally I tend to run most apps fullscreen most of the time, switching between them with keyboard shortcuts.

I started with i3 Window Manager, which is a really nice piece of software. After a few years of using it though I realised I didn’t use most of its features, so landed on the very minimal Suckless Tools DWM.

With workspaces, each app can have its own screen and can be accessed instantly via a keyboard shortcut. With familiarity this becomes a chord in muscle memory, a hand-shape to mash at keyboard. I have habits for where I keep each app, so eg my terminal is in workspace 1 so [Alt]+[1] puts me in the terminal. [Alt]+[9] puts me in FireFox and so on.

I’ve [Alt]+[Tab]bed through apps in the past. Workspaces are similar except you know the keyboard chord will take you directly to the app you want, you don’t have to play ‘stop the magical app carousel at the right time’… which may be a drawback for some I guess, as carousels can be fun.

We can only focus on one thing at a time, that’s how attention works. I can see some uses for multiple screens eg if you have to monitor lots of things, like real-time charts or meters. In that case your peripheral vision is good at detecting change/motion so you can make use of all the space. But personally I’m completely over large/multiple displays. In my circumstances, they waste power, waste space, and are just not necessary.