Linux

I added an entry to ~/.ssh/config so I could scp images from my desktop to my Pixel 6 (running Termux’s sshd), and I put a User in it. Then I noticed: when the other end is Termux, ssh banana@<phone> and ssh root@<phone> both log in as the same user. The User line in ~/.ssh/config does nothing. It’s not a config problem — it’s how Termux’s OpenSSH is built. First, the observation $ ssh -p 8022 banana@100.65.202.69 'whoami' u0_a440 $ ssh -p 8022 root@100.65.202.69 'whoami' u0_a440 Copy banana and root both connect, and both land as u0_a440 (the Termux app’s user). The key is checked only against /data/data/com.termux/files/home/.ssh/authorized_keys. ...

Around the time I bumped Neovim to 0.12.4, nvim-treesitter errors started piling up one after another. Tracing them all leads back to a single fact: nvim-treesitter’s master branch is already EOL and can’t keep up with Neovim 0.12. Migrating to the main branch fixed it, but here’s the path there — plus one more pitfall I stepped on after the migration. Environment: Item Value Neovim v0.12.4 (Arch Linux) nvim-treesitter master (tag v0.10.0, frozen May 2025) → migrated to main Plugin manager Lazy.nvim Symptom 1: Opening Markdown crashes on a gotmpl parser The moment I open a Markdown file, it halts with an error (Press ENTER or type command to continue). ...

The symptom On my everyday swayfx setup, bringing a scratchpad window up and then hitting scratchpad show a second time (the toggle’s “hide” path) crashed the whole compositor. It threw me all the way back to the SDDM login screen — a loud crash. Environment: Item Value swayfx 0.5.3-4 (based on sway 1.11.0, Arch Linux package) wlroots 0.19.3 GPU AMD Radeon RX 6600 XT (amdgpu) The bindsym was: bindsym $mod+minus scratchpad show, resize set width 90 ppt height 90 ppt, move position center Copy scratchpad show chained with resize and move in one command. Press it twice in a row (first press shows the window, second press is hit while it’s still focused, which takes the hide path) and it crashes. ...

Correction (2026-08-08) The original conclusion of this article — “this cannot be resolved through user configuration” — was wrong. Setting IME environment variables in /etc/environment made Ctrl+Space work for direct input. If you only want the fix, jump to Update: Solved. The investigation below is kept as-is, as a record of how I reasoned my way to the wrong conclusion. Symptom Pressing Ctrl+Space (the fcitx5 trigger key) in Street Fighter 6’s chat box does not switch to Japanese input (Mozc). Text stays in romaji and nothing responds. ...