Before I sold my FC660C, I took it apart and lubed the sliders a few times with trybosis 3204. It was my first time taking apart a keyboard and wasn’t particularly difficult and the stabilizer keys are really just wider regular topre keys. There is a wire, but it’s inside the key instead of over top like cherry. A good set of tweezers is all you need. There’s a good video by Taeha Types about lubing an HHKB which was not all that different. I’d say the most tedious thing about it was just how many screws there are holding the PCB to the plate

A few things to watch out for:

• be careful about the ribbon cable that goes from the main board to the daughter board that has the usb port on it
• try and keep the domes from separating from the PCB. there shouldn’t be any reason to remove them and they’re held in place with some sort of adhesive. I’ve heard if you take them out then it’s a pain getting it all back together.
• if you take the sliders apart you may break some plastic tabs on them, but that’s normal so don’t worry (see any video about lubing topre)

Feel free to reach out if you have any specific questions! :)

I may be wrong but I believe that all of the systemd programs are decoupled. You can run the systemd init system without any resolved or networkd. They just happen to be used by default on a lot of distros.

Mechmarket might be a good place to check

No worries :)

Here’s what I found on the readme on the nvim repo

Catppuccin is excellent in terms of features, plugin support, and customizing highlight groups/palette colours

Convenience is often a tradeoff for power. Nobody is claiming that vi and its derivatives are convenient, they’re saying it’s powerful.

Personally I’m much much faster using neovim than I could be using something like vscode. There’s a myriad of other benefits that modal text editing brings to the table, not having to use a mouse and constantly switch back and forth being a big one for me.

I haven’t fact checked this at all but apparently lowprokb.ca is working with Kailh on some choc v1 compatible silent switches which could potentially be used in those boards. Not sure when they’ll be available though

I believe the reason is that bash is backwards compatible with sh and sh only has [ ], not [[ ]]

Try putting # vim:ft=yaml.ansible at the top of your file then re-opening it

Can you paste the output of :LspInfo when opening an ansible file? Wait a few seconds after opening the file to give the language server time to load

I don’t know about OP but personally I run nvim on 3 systems (4 if you count termux on my phone) and it’s very nice being able to test out a config and plugin updates on my personal systems before pulling down the changes on my work laptop so I know everything just works™

I don’t actually use LazyVim, but I do use the Lazy plugin manager

Not op; I don’t use LSPZero but the built in support with lsp-installer. I like to think I’ve organized my repo decently well so hopefully it can help you out: repo

I used to use CoC a looong time ago so I don’t know if this has changed since but I’ve heard LSP is faster than CoC and has better support since it’s the defacto standard for neovim (and built in). Additionally it uses the same binaries used by something like vscode for the analysis so it’s part of a larger ecosystem that will get support

Using shift+hjkl for 10 line jumps you lose J to combine lines which I find myself using a lot. Do you have those kind of things bound to something else or do you just not use them?