Over the years I’ve picked up various tweaks for my nvim configuration. One of them is template file support. This article is a short introduction to what they are, how do they work and how I recently extended them to support snippet expansion.

In this post I want to show you how you can debug Lua scripts with Neovim and nvim-dap. Both regular Lua, but also Lua that uses Neovim as Lua interpreter. The latter is interesting if you want to debug Neovim plugin test cases written using busted

Recently a change got merged in Neovim that decoupled its TUI from the main process. A side effect of the change is that debugging it became a bit more troublesome. It now forks itself and you end up with two processes. Depending on what you want to debug you need to attach to that second process.

I thought this might be an interesting use-case for more advanced features of nvim-dap. This post explores using it to automate attaching to the second process.

Even if you’ll never debug Neovim you may find this interesting as it could give you some ideas on what you can do with a hackable debugger.

This post uses nvim-dap features of the upcoming 0.5 release. If you’re on 0.4 you’ll have to switch to the development branch. (If you are from the future, use 0.5+)

This is a short article covering how you can use Neovim as Lua interpreter for Luarocks and busted.

This is an introduction to the various ways you can structure a Neovim plugin and their trade-offs.

This is a short introduction in how you can test a Neovim plugin which extends the LSP functionality. This approach requires Neovim 0.8 or later.

Neovim 0.8 got released the other day, time to write about some of the LSP changes.

As part of my work on CrateDB I occasionally have to debug its PostgreSQL wire protocol implementation. One tool that has been incredibly helpful for that is tshark, which is part of Wireshark.

This is a short introduction to the tree-sitter integration in Neovim based on a use-case I had: To find content in a TOML file close to the cursor position and then launch an application using this information.

A recent conversation got me curious about how people feel about writing command line applications in Java.

I knew that Java for many isn’t the first choice when thinking of building a CLI, but I was curious if people consider it an option at all. I started a poll on Twitter. Only 19 people participated, but the outcome was quite clear:

Java is a good choice to write command line applications

If you asked me several years ago I’d have had a similar reaction, but in 2022 I’m not so sure anymore.