Tootfinder

Things I've learned today:
- Valgrind does not support AVX512 instructions. That was an adventure because I was writing purposefully bad code at the time...
- However, changed strategies and used `clang` with the `fsanitize=address,undefined` option which seems to work perfectly fine.
#clang

Just pushed through half of Rustlings out of boredom even though I already know how to code in Rust (I forgot I have a project to make).

God, what a fucking asshole.
Anyways, I've already spent some time removing #neovim from about half of my build/development containers. For now I'm going back to #vim, but once vim-classic or #evi

I've streamlined the way #Neovim manages my LSP, Linting, and Formatters. Just sharing my approach with you in this #post:
https://

> GPU-Accelerated Emacs Powered by Rust
Aka how techies fail to address a single real problem. Emacs community deserves their own neovim-like movement, but neomacs isn't one.

The Zig journey continues, things get a bit cleaner and we're now parsing the primary partition entries in the MBR. Very nice...
#programming #zig

I've rebuilt my #neovim config to benefit from version 0.12 and I've learned some new things in the process. Beyond what has been reported everywhere already, here are the small tips I'd like to share with you:
https://

Q: Where is the code? What you've been doing whole day?
A: Figuring out why kewords are red instead gruvbox aqua blue in my #neovim
Q: Oh I see, carry on!
vim.hl.priorities.semantics_tokens = 95
You can take my treesitter syntax highlighting from my cold, dead hands.

Moar progress, will probably move this into the struct along with MBR reconstruction from the struct. This might actually end up doing a bit of `fdisk` stuff...
#zig #programming #mbr

Rework my #Neovim config to finally benefit from the recent major changes. Since I was on it, I've also revisited the entire config, some plugins, replaced some with simple functions... It was a lot of fun. It's been a long time since I had a chance to tweak Neovim that much and it felt good :)

To come so far with hyprland on FreeBSD (it's working!) and then that Danish fuck spoils any party 😡 Really in doubt whether I should publish at all. Which means I probably won't.
I'm all for devs being paid, even by big business, but active association with a white supremacist is a new level of 💩. Btw, neovim has been called out also. I'll be reviving my River and Mango FreeBSD repo's in the meantime.

🔧 Ships as a language server (harper-ls), a JavaScript library, a Rust crate, browser extensions and editor plugins: VS Code, Neovim, Zed, Obsidian, WordPress block editor, Chrome, Firefox and a macOS desktop app that works in every text field system-wide.

So, after searching far and wide on the internet I have managed to open a file from a command-line argument and read 10 bytes from it using Zig v0.16. I was not expecting it to be quite this complicated.
#programming #zig

Looks like I got a little ahead of myself. My last post about my new #neovim config left out quite a bit of what I wanted to share. Better late than never, time for an update! ^^
⁨https://www-gem.codeberg.page/vim_2026…

Yes. So, when I got Hyprland going on FreeBSD, there was more to learn.
Decided to use ashell as a bar, rio-terminal, wezterm, nwg-drawer, walker or good ol' rofi, neovim, you name it🤣 Rust and lua.
The curious mind can be a burden, as well as a pleasure 😄
It'll take some more time, but everything is up and running. Having a great time!
#freebsd

Freedom of speech, unless you don't share my views.
There's a good reason Soviet gulags and prisoner transports were always full.*
*I know it was mostly not about freedom of speech. It was about needing forced labor.
#neovim