I recently starting using asyncomplete.vim for vim completion with LSP servers. I initially tested it out just to see if it would be more responsive than manually invoking vim-lsp’s completion (which sometimes takes a moment regardless of async because I don’t proceed until it’s done) and found that it seemed improve responsiveness – presumably because the completions appear once their available instead of when I request them.

This is my summary of a talk by Alex Jaffe.

A vim colorscheme determines how all UI elements are coloured. Try :help group-name and you’ll see the colours used for each kind of token in your code. With your current colorscheme, you should recognize the colours you like displayed with vim’s name for those tokens (the left column).

I tried out three vi emulator extensions and these are my notes.

I saw this tweet asking gamedevs for gifs and read through a lot of the replies and was struck by how many of the pitches didn’t have enough to hook me on the game. As an exercise, I tried to figure out specific improvements to these pitches or must-have elements for a pitch.

For context: I recently shipped a game translated into 14 languages and I was the programmer who adapted our translation system from another game, updated our game to use the system, and managed importing translations.