Enno Konfekt

Note: This gist is now part of VimBits plugin.

As a Vim user, you might prefer the new vim9script over the legacy script, and wish to use it in the command line. While there's no direct option to switch the command line to parse vim9script, you can execute vim9script commands by simply prepending each command with vim9.

However, remember that execution occurs in the global context, not the script-local context. This means you need to declare variables with the g: prefix, like g:foo = 'bar'.

Common commands such as visual mode select ('<,'>), shell commands (!), substitution (s//), and global (g//) work as expected, even with vim9 prepended.

My gvim toolbar

Making a Nice ZSH Environment

Making a Nice ZSH Environment
zshenv

Linux Desktop Issues

This is basically my manifesto of why Linux sucks and I keep using Windows as a desktop OS. This is both as a developer platform and end-user targeting.

Look: I would love to be able to use Linux as a daily driver. KDE is amazing and they clearly put far more effort into the desktop experience/UI than Windows (just the volume mixer alone). There are simply far too many underlying and infrastructural problems to the Linux desktop that none of KDE's great UI changes can make up for. I want Linux fanboys, developers, etc... to stop sticking their damn head in the sand about these issues and admit that Linux is still decades behind in some basic infrastructure. This shit can't get fixed if people refuse to admit it's broken in the first place, which some people are far too happy to do.

Desktop App Experience & Developer Tools

Windows has far better desktop apps than Linux, and thanks to WSL, I have all the CLI apps of Linux too. While I do believe KDE Plasma is a much better desk

	PROMPT FOR LLM (copy+paste below, then append your plan)

	You are converting a generic plan of action into a production-ready research/engineering `todo.md` that is directly executable by a capable coding agent. Your output must be a single Markdown document with a fenced XML `<workflows>` block. Do not include any extra commentary, explanations, or chat—output only the document.

	### Transformation requirements

	* Be specific and operational. Replace vague goals with concrete steps, commands, checklists, acceptance gates, and explicit assumptions.
	* Prefer compact, high-signal prose. No filler. Use short paragraphs and terse bullets.
	* If information is missing, make minimal, clearly labeled assumptions (e.g., “Assumption: …”). Do not ask questions.
	* Compile the spec into executable oracles: pre/postconditions, invariants, consumer/provider API contracts, and metamorphic properties. Generate both tests and runtime guards.

	#!/bin/sh

	# Adapted from:
	# https://github.com/ficcdaf/academic.nvim/blob/83865969059b2aaea2e7afcebaa60085e965d9f8/scripts/generate-wordlist.sh

	# Adjust to your home directory:
	VIM_HOME="$HOME/.vim"
	DOWNLOAD_TARGET="$VIM_HOME/spell/en-academic"

	# The "unmunch" command comes with "hunspell":

	% Options for packages loaded elsewhere
	\PassOptionsToPackage{unicode$for(hyperrefoptions)$,$hyperrefoptions$$endfor$}{hyperref}
	\PassOptionsToPackage{hyphens}{url}
	$if(colorlinks)$
	\PassOptionsToPackage{dvipsnames,svgnames,x11names}{xcolor}
	$endif$
	$if(CJKmainfont)$
	\PassOptionsToPackage{space}{xeCJK}
	$endif$
	%

	#!/usr/bin/env bash

	# shellcheck disable=SC2207

	base_url="https://github.com/$user_name/$repo_name/releases"
	pkg_path=$(pwd)
	distro=$(uname) # Linux / Darwin
	arch=$(uname -m) # x86_64 / aarch64 / arm64

	help() {

	# ETC
	*/certs/

	# INCLUDE

	# General
	.DS_Store
	.AppleDouble
	.LSOverride

	#!/usr/bin/env python3
	"""
	Fix moved/renamed files before running rsync to avoid useless retransmissions.

	Copyright (C) 2022 Anton Pirogov, licensed under the MIT License
	"""
	from itertools import chain
	from typing import List, Dict, Optional
	from dataclasses import dataclass
	from pathlib import Path