Sway sort of does that. It does not resize live, but uses a transparent overlay to show where the window will be. You can do all of the moving and resizing with the mouse this way.

I do not know the answer, but this got me thinking: would it be easier to set up a single login for both session and decryption if /home was on a separate partition and only /home was encrypted?

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.

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.

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.