Reply in solidarity.

Reply in solidarity.

that's like a man trying to explain to a woman how an erection feels, I.e. good luck with it

That's easy. She just gotta hold her hand out.

When I want to add an automatic garage door, I don't go on r/ElectricalEngineering and ask how rewarding learning EE can be. I decide wtf I want to have happen, then google accordingly.

Easy there fella and try not to get the pages stuck together.

With that out of the way...

Your life story wasn't in the way until you put it there.

Your question could be condensed to "use-package is extra bureaucracy when you need to do something non-trivial, e.g., reconciling two packages' config."

I found use-package impenetrable as a noob. It only started making sense after I learned the subtleties of minor modes, autoloads, keymaps, custom variables, etc., at which point use-package became superfluous macro alchemy. Judicious use of `eval-after-load' is all you need and a lot less wtf.

Even if things weren't broken now, they will be in a couple months. If you take the fragility of emacs to its logical conclusion as I have, you end up writing emacs instead of writing software.

Diddling python is but an intermediary phase to non-coding management, but diddle you must to prove you've been in the trenches. Alas many a doughboy fell under emacs's hypnotic spell and never poked their heads out to see the war's been long over.

Have tried both and must agree.

> I can tell that I've noticed some improvements.

I can tell this claim is worthless without data.

Needs more rainbow, but yes, this feels very on-brand.

Needs more ghey.

For this old timer, emacs achieved nirvana with version 19.34 (hilit19 anyone?), when RMS and his merry men retook the crown from the Lucid pretenders. The 19 series were like the last of the air-cooled Porsche 911's contemporaneously in vogue. Things stabilized with versions 20 and 21, then languished until some pretty lousy but well meaning programmers revitalized development in 2008.