When choosing a bug, if you start with one that is possible to reproduce, it might help following the instructions to reproduce it while debugging the app and observe what happens. This can be a way to start understanding how it all runs. Bugs without context or hard to reproduce are usually more complicated and you might need a better knowledge of the code to have an idea of where to look.
Pierre
joined 1 year ago
That is incorrect. Both are pretty barebones from the start and have a big pool of extensions to get the functionality that you need. It might be more involved on the vim/nvim side, but that is more of an accessibility VS personalization thing.
There are even sort of distributions for nvim that bring you all the common functionalities already configured.
I only have limited experience on that topic, but when I had to set up my printer, I found the arch wiki very helpful: https://wiki.archlinux.org/title/CUPS
Packages name might not match, but general info should be good for any distro.
I went with a used ThinkPad yoga 370. It still only has a dual core while the following Gen has 4 cores, so it seemed there was a price gap. It has thunderbolt 3 for when I want to switch to a bigger screen (with a cheap USB c dock) and USB c charging. Also I wanted to try a touchscreen on a laptop. I should be able to upgrade the single ram stick in it at some point. Running arch with sway without problems.
Edit: I had a x240 for years before. It was fine but I appreciate the higher resolution of the 370, even if I ended up using fractional scaling as it was just a bit too small.