Bernie @[email protected]

@qy Ah, the config was moved to .config/nvim for XDG compliance. To share the old vim config, simply do:

mkdir -p .config/nvim && ln -s .vimrc .config/nvim/init.vim

@qy If what you most liked about vim was its expressive editing commands, none of that is changing in neovim. In fact, I can't even tell which one I'm using if I'm just editing plain text (but I depend on neovim plugins for semantic code completion in C++ and Rust).

Give it a try, tell me if you find anything that works differently.

@qy uh? Where did you get that neovim requires desktop? The devs started the development by deleting 30% of old cruft from the vim codebase, including all the built-in GUIs.

What was added back, in terms of dependencies, is just low level libraries for asynchronous I/O (libuv), protocol serialization (msgpack) and terminal emulation (libvterm). All these libraries are bundled, but most distros chose (wisely, imho), to package them separately.

@angdraug Someone should go tell the Arch guys who've been struggling with the Sound Open Firmware updates that all they had to do is delete it and use an older kernel 🙂

@espectalll @QuestForTori Perhaps I dropped it sooner than that... I vaguely remember that I got bored when it became mostly just fights...

On my way back from Italy to Japan, I could do a 2-3 day layover in Moscow for free. But it's winter... 😰

@benoit @espectalll 🤩

@amdt @benoit Actually, 尺八 could have more likely meant the flute in that example...

https://en.wikipedia.org/wiki/Shakuhachi

Being both a physicist and an avid gamer, Scott Manly has a unique approach to scientific coverage. Here's what I mean:
https://www.youtube.com/watch?v=bwZHzKnEEs4

@QuestForTori I don't quite remember this scene... which episode is this?

@espectalll rob deserves public shaming for this...

@shahaan And note, when hardware support is still bleeding edge on Arch, it will typically take 6 to 12 months before it works out of the box on Ubuntu, Fedora, and any other non-rolling distros.

#KDE Frameworks releases don't get a lot of attention, not being an end-user product, but a lot of work goes into maintaining and improving these libraries. Just check the release notes...

https://kde.org/announcements/kde-frameworks-5.65.0.php

For example, I had no idea the ThinkPad X1 Carbon Gen 7 had a quirk with the microphone that requires a very recent kernel and additional tweaks in userspace 😲

I'll buy it anyway, but good to know...

https://wiki.archlinux.org/index.php/Talk:Lenovo_ThinkPad_X1_Carbon_(Gen_7)#Microphone

And another important shopping tip: before buying any laptop, always check the #Arch Wiki for Linux compatibility quirks!

https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_7)

@benoit Guaranteed to stick to your memory...

@espectalll And now there's the LanguageServer protocol to rule them all. All editors support it, all languages are supported. Thank you, Microsoft ❤️

@espectalll but anyway, if your extensions are executing a ton of vimscript, they're doing it wrong. Complex extensions such as semantic completers for programming should talk to a daemon over some socket protocol. Neovim provides msgpack to simplify protocol encoding and decoding.