* Windhawk - can tweak taskbar with extensions similiar to gnome tweaks imo (free)

* DisplayFusion - qol for multi monitor setups (paid)

I would give it a try if these two applications help you, honestly there's just so many settings to explore -- but afaik static width was something I needed and got done through Windhawk.

Could I prod why that is? I'm dealing with a ovh server and using their anti-ddos detection for an issue currently so this topic I'd like to learn about.

I think I would be half as productive as I'd like without this.

I think on retrospect deadlifts may have been my issue to, I did the deadlifts that day and later remember going to pickup something off the ground and getting the issue. Not sure if the deadlift was the cause, but I always thought my muscles were sore/tired and lax, thus when I went to lift the thing my lower back stability was compromised.

I'll try Romanian deadlifts and those other exercises, thanks for that suggestion.

Deadlifts also helped strengthen lower back muscles. Tight hamstrings from sitting on the computer all the time also didn't help. I'll try dead hangs.

I don't even know what to reply to here, but I'm in general agreeance with most of what you wrote. I just don't agree users type "vim" alone their first time, I'd wager it's following some guide/tutorial online that already has 'vim filename.txt' snuck in there. The fact that people get stuck in vim feels like something intentional to weed out people, otherwise it's a funny problem people run into on other programs like ftp, ssh, screen, even the python interactive shell. There's no unified lexicon on cli tooling, except maybe the gnu clis. It makes you appreciate good GUIs.

The real big brain approach here is to divorce the idea of vim from the command line editor and use it as a plugin in an IDE. Best of both worlds.

If you open vim with a file, like you do with all file editors, there's no such examples. It's also at the bottom of auth/credit/contribution fluff in your example, which people would be expected to ignore.

> Because you can't read

I'm not arguing for more hand holding here, but saying the poster can't read is ironic. Reading is one part, comprehending is the other.

I've seen just a general recommendation to avoid urlencoding parameters -- I guess that's why?

I wonder if there is negative side effects of this though, do you notice when interacting with people who speak slower require a greater deal of patience?

I think minimalism/no buy movements are big though.