OBender

I've been doing some recreational #homelab -ing (my own term :D) over the weekend. Though the results are not a world class achievement, yet I'm so happy and excited it worked. IT has been a while since I had fun configuring #linux servers. If anyone's interested about the setup, see the thread below.

I had to upgrade to macos #Tahoe on my work laptop. I've been a fanboy of everything Apple company has designed for years, and I won't bring the "Steve era was good" here, because it's silly. But maaaan, who told these guys, that so f-in much rounded corners are ok, that's to say the least? And don't get me started on apple intelligence. I'm so much frustrated to work with this for the remaining of time, ugh.

I just can't help it, must share this with others 😅 . My custom (missing for years) key binding for #neovim :

map("n", "<leader>fom", "<cmd>!open -R %<cr>", { desc = "Open current buffer in MacOS Finder" })
map("n", "<leader>fym", "<cmd>let @+ = expand('%')<cr>", { desc = "Yank relative path to current buffer" })

Day 2 of playing around with #lazyvim distro. This time I've pushed myself to go through the official docs, completely. "Solid" - is the least I can say. I've always been a fan of doing my own setups and proudly stick with them, but this time I'm seriously tempted to use the offered one. The journey continues. #neovim

I'm stuck on the point where my #neovim config regularly breaks whenever I do an #lazynvim (plugin manager) update. I'm aware about the lockfile and restore functionality, HOWEVER, I would really appreciate if people share their way to keeping their neovim sane and in working state , so please ↓

I've been reflecting a lot on the #privacy and #ux portion of the desktop & mobile software recently. It's kind of funny how the world went to cloud-first software almost everywhere. This needs to change.

The saga with my #neovim config continues. I already re-did it many times throughout my vim journey, however everytime instead of doing it clean and right, I just quit since it kinda worked, which is the goal, right? Anyway, I've got this great book from my friend who brought me into a rabbit hole of #kinesis keyboards and (neo)vim (thanks @gemelen@mammut.moe). I've read it many times, yet everytime I learn something new, like today I've learned it's possible to undo changes fot the last X minutes, cool!

nobody: .... me: it's time to redo my whole #neovim config decided to try out some of the distros, Lazyvim it is. Let's see what happens next.

@gemelen@mammut.moe absurdity at it's best 😁