tshepangso good to see that Helix is now packaged in Debian
Renewable SexcellenceI just completed "Laboratories" - Day 7 - Advent of Code 2025 #AdventOfCode https://adventofcode.com/2025/day/7
Like I expect most people, I found that a purely recursive strategy worked fine for the test input on part 2, but took an unrealistic amount of time on the real input. So I figured out that if you ever get to a point where another beam has reached, the result from then on is the same, and so we can cache.
I had a lot of faff working out how to pass the cache object (just a HashMap) around functions while keeping it mutable. Turns out that #Rust needs you to declare something as mutable:
and I had missed out the second step.
Also, I figured out how to get rust-analyzer integration working in #HelixEditor which means I'm now learning how to use Helix properly.
hardtech.ftsIn 2026, I want to change my OS. I'm hesitating between
- Arch
- Devuan
- Gentoo
- Guix and
- Void
Things to consider:
- I've already installed and used Arch some years ago; I'm considering Artix, excluding the s6 init (I'm not prepared for this one);
- gentoo and Guix are probably the most complex distros1
- Void is certainly the most comfortable choice.
- It's to install in real hardware: Intel i5-7400 3ghz, ssd 1to, 32gb ram, nvidia geforce 1060 3gb. Yes, I want to play light videogames sometimes
Main purpose would be to learn Linux, Web, writing MarkDown and Org, zettlekasten organisation, etc...
#linux #archlinux #ArtixLinux #devuan #gentoo #GuixSystem #voidlinux #emacs #doomemacs #vim #orgmode #orgroam #vim #HelixEditor #zettlekasten
1: complex ≠ complicated
@liw @c3 @kinnison Apparently the thing I was missing was running rustup component add rust-analyzer rust-src as per https://wiki.debian.org/Rust#Using_Rust_Analyzer to get #Rust hints working within #HelixEditor.
Now I just need to understand them...
Trey Piepmeier@carlton @tobide @davebauerart I've tried several times over the years to switch to Vim, but it never clicked. #HelixEditor finally did it for me. I'm finally off VS Code. The key factors for me were the contextual help (automatic keyboard shortcut documentation) and the fact that it's an IDE out of the box. So nice!
WolfFor various reasons, I build #HelixEditor from source (at least weekly). This turned out to be the reason why I (confusingly) wasn’t seeing syntax highlighting in certain situations. When you put yourself in charge of building the editor, you will also often have to fetch and build all the grammars. #TIL (well … yesterday, anyway)
@gotofritz For instance, in my team everybody else uses #PyCharm (which **can** use an LSP, but they typically don’t and if they did maybe they would choose a different one). I use the #HelixEditor.
You are right. We should all use the same tools to the extent possible. We should all see Python type errors while editing. I should absolutely convince them this is valuable outside of `pre-commit`.
Valentin B. 
Bobulous 
@resplendent606 I use the Helix editor for Rust development, and for writing HTML pages, and it works really well. I never could make sense of Emacs or vi[m].
One of these days I'm going to have to kindly ask @c3 or @liw or @kinnison to explain #Rust typing to me properly.
I am currently stuck on #AdventOfCode day 6 because something I think should be a HashSet<usize> has ended up being a HashSet<&usize>.
My current approach of just brute-forcing .try_into().unwrap(), .collect() and other postfixes until something works is failing here.
Or maybe I need to actually get #HelixEditor or #VSCodium set up with Rust better idk.