TL;DR Use kanata when your qmk keyboard is not around. Introduction I have a qmk keyboard bought from keebio (note: highly recommend!): However, sometimes I’m on the go, and I’m forced to use my laptop keyboard. After being spoiled by qmk’s insane customizability, I couldn’t go back to a regular keyboard. I found kanata and kmonad and they could simulate most of my qmk experience. Why kanata over kmonad? The exact reason Why I built and use kanata....

TL;DR If you want to use plocate while your filesystem is btrfs, do the following: edit /etc/updatedb.conf: replace PRUNE_BIND_MOUNTS = "yes" with PRUNE_BIND_MOUNTS = "no" save the file update the db with sudo updatedb test again with $ locate home to see any outputs from home directory Introduction plocate is supposed to be a much faster drop-in replacement for mlocate, but I had a lot of troble getting it to work....

TL;DR Stack: Nextcloud: server tasks: Android client Todoman: cli integration vdirsyncer: “database” Together they can sync across your Linux desktop and Android devices. Introduction Why switched away from Todoist? Proprietary No cli integration Notes The above solution does take some time to set it up. But afterwards, it’s set-and-forget. Also, check out my How to Migrate From OneDrive to Nextcloud to get started on Nextcloud. Tools Nextcloud: server that glues everything together tasks: Android client on the go Todoman: cli integration vdirsyncer: synchronizes TODOs between devices autovdirsyncer: monitors the TODO db and update accordingly and automatically Getting Started Install the packages pacman -Syu todoman vdirsyncer autovdirsyncer Notes The binary for todoman is todo....

TL;DR Use find-extender.nvim to jump to anywhere within the current line with exactly 4 keystrokes. Introduction Using leap.nvim to jump to any location within the buffers is great but for jumping within the current line, I didn’t have a good enough solution until now. I tried clever-f.vim and flit.nvim but they’re not precise enough. Let’s say I have the following line and have to get to WORD_fingWORD: print("find FInd fInd find_extender WORDfiWORD wordfIword WORD_fingWORD") The annoyance is that when my eyes are on the target string, I’m not aware of all the possible matches preceding WORD_fingWORD....

TL;DR Use sway-toolwait to control the layout and workspace of your autostart apps. Introduction I used to have the following in ~/.config/sway/config.d/autostart_applications: swaymsg "workspace number 1" swaymsg "exec flatpak run --env=OBSIDIAN_USE_WAYLAND=1 md.obsidian.Obsidian" swaymsg "exec kitty" swaymsg "workspace number 2" swaymsg "exec firefox" swaymsg "workspace number 3" swaymsg "exec chromium --ozone-platform-hint=auto" swaymsg "exec kitty" swaymsg "workspace number 4" swaymsg "exec vieb --enable-features=UseOzonePlatform --ozone-platform=wayland" swaymsg "exec kitty" As you can see, I have 3 Chromium-based app....