lmno-lol-iivfpk.txt (3530B)
1 [1]@puddingtime 2 [2]sign in · [3]lmno.lol 3 4 _____ _____ _ _____ ______ _ _ ______ ______ _____ _ _ _____ _____ _____ ___ ___ _____ _ 5 |_ _||_ _|( )/ ___| | ___ \| | | || _ \| _ \|_ _|| \ | || __ \|_ _||_ _|| \/ || ___|| | 6 | | | | |/ \ `--. | |_/ /| | | || | | || | | | | | | \| || | \/ | | | | | . . || |__ | | 7 | | | | `--. \ | __/ | | | || | | || | | | | | | . ` || | __ | | | | | |\/| || __| | | 8 _| |_ | | /\__/ / | | | |_| || |/ / | |/ / _| |_ | |\ || |_\ \ | | _| |_ | | | || |___ |_| 9 \___/ \_/ \____/ \_| \___/ |___/ |___/ \___/ \_| \_/ \____/ \_/ \___/ \_| |_/\____/ (_) 🔥🤘🏻🔥 10 11 June 19, 2025 12 13 [4]Helix 14 15 I had insomnia a few nights ago, so I started fiddling with different things, 16 including the CLI tasks tool dstask, which is sort of TaskWarrior without the 17 misanthropy. (I kid.) 18 19 So a kind of nice thing about dstask is that with dstask #{note number} note 20 you pop open $EDITOR in a Markdown note attached to the task. dstask is aware 21 of any Markdown checklists inside the task note and blocks completion of the 22 task if there are open ones. 23 24 That's maybe bad for me because I am a compulsive subtask-maker with a bad 25 habit of opening a task, loading the subtasks into my buffer, and just doing 26 them all without looking back. So if I stick with it dstask may shape my habits 27 that way. 28 29 For some annoying reason, dstask also barfs if $EDITOR has an argument, e.g. 30 emacsclient -nw, and I found myself once again writing some kind of wrapper for 31 emacsclient. That is not Emacs' fault, but it raised the perennial question 32 "when does $EDITOR come into play and do you need a whole-ass Emacs config for 33 those times?" 34 35 So I think "your go-to for this used to be jed, which acts like Emacs where it 36 matters." But I've been using evil in Emacs for years now: If I want to keep my 37 muscle memory between quick CLI edits and my whole-ass Emacs config, what I 38 really need is something from the vi family. 39 40 It being 3 in the morning, I embark on a tour of modern vi's, looking for some 41 sweet spot of "nimble" and "feature-packed." I burn through a few neovim 42 tutorials and starter kits (nooooooope) before stumbling into a feud between 43 neovim people and Helix people on reddit. 44 45 So around 4 I'm running brew install helix and going through :tutorial. 46 47 It's pretty nice! It launches quickly. No plugin system so the futzmonkey sort 48 of has to stay in its cage, but it's very batteries-included. I found a [5] 49 tutorial for setting it up for Markdown that wasn't overwhelming and helped me 50 get a sense of how its config works. 51 52 It is not "just a batteries included vim." It has its own keybinding grammar 53 (subject/verb, not verb/subject), so after bonking my head on those changes a 54 few times I [6]cheated and lifted a few vimisms. 55 56 I guess I also went through a quick consideration of micro, but the CUA-style 57 default keybindings confused me the way nano often confuses me. 58 59 60 61 powered by [7]LMNO.lol 62 63 [8]privacy policy · [9]terms of service 64 65 66 References: 67 68 [1] https://lmno.lol/puddingtime 69 [2] https://lmno.lol/signin?goto=/puddingtime/helix 70 [3] https://lmno.lol/ 71 [4] https://lmno.lol/puddingtime/helix 72 [5] https://helix-editor-tutorials.com/tutorials/writing-documentation-and-prose-in-markdown-using-helix/ 73 [6] https://github.com/LGUG2Z/helix-vim/blob/master/config.toml 74 [7] https://lmno.lol/ 75 [8] https://lmno.lol/blog/privacy-policy 76 [9] https://lmno.lol/blog/terms-of-service