Vim>overrides .vimrc settings with dozens of autocommands>ignores certain autocommand events like buffer commands for the initial buffer>set indent rules in vimrc>filetype autocommand overwrites them by default>opinionated as fuck and opinions are all shit>forces opinions via obfuscationi tried for 1 1/2 hours to set t_CO=8 in vimrc and gave up. wherever that variable is overwritten is buried deep in a truckload of spaghetti. after searching forums the only working solution i found was downloading a theme that only uses terminal colors by reference that somebody had to create to work around this problem. vim is misbehaved garbage that relies on messy hacks to do anything sane.emacs>ignores desktop scaling settings for only half of ui>have to set font to twice normal size to fit ui>larger font size fucks up frame column and line count>gui spazzes out and becomes unusable>only works in terminal (-nw) which is fine for me>community packages ignore or assume termcap 99% of the timetrash piled upon trashhow is it that both of these editors were fine 10 years ago and now they're broken garbage? i used vim for half of my life and never had these problems until the last couple years.
>>108690853i autoload a project specific vimrc in my project folder where i set any defaults i want for the project/language. it gets loaded after my user .vimrc.no issues you mentioned.
fake and gay comrade, fake and gay.are you retards even thinkin when posting the same fake trash in here? why are you so poor? at least generate something with AI (show nice beautiful layouts)
>>108690853>linux is vim and emacsgood post OP
>>108690853>>larger font size fucks up frame column and line countpic?
>>108691016i don't know how to capture the problem with a pic. if i tell it to resize the frame to 80 columns it resizes it it 53 like it doesn't have the size of the font right. it only happens when i use the window scaling option in xfce. when i disable window scaling it works fine. everthing scales correctly except the content frames or boxes whatever.
>>108691053
>>108691001those were just 2 examples>opensuse install iso repeated kernel panic during boot>ubuntu installer fails to see hd and reliably hangs at network connect step>suspend is a crap shoot>3x more ram needed for desktops with fewer features than they had 10 years ago>buggy inconsistent resolution scaling on everything but kdeetc
>>108691101use real distros (debian/arch/fedora/mint) and you won't have these problemsother problems aren't really getting worse, and 3x more ram use than 10 years ago is definitely not a linux-specific thingwayland has been rough, luckily you can just stick to x11
>>108690853vim is vibecoded trash these days, do not updatedrew is a retard but he was right to fork it>opinionated as fuck and opinions are all shityou might be retarded too
>>108690853Are you using gayland or something?
>>108691508whatever the debian xfce task defaults to. i'm guessing x11. what's odd is that vim only has problems with vimrc at startup. when i source it with ":so %" it works as expected. i'm not sure how xfce window scaling is implemented but i know emacs scales properly in gnome and kde so it's probably an xfce problem.
>>108690853Vim is accepting LLM garbageEmacs has always been a GNU meme in my opinionneither is Linux. shit like Pipewire is gooduse NeovimOP is a fag
>>108690853>gui spazzes out and becomes unusableRecently, on one of my laptops, I've experienced Emacs getting into weird states where keyboard input get's fucked up. It only happens in X11 though. On my desktop which is also using X11, it's fine.Back to my laptop, I switched to Wayland and the weird input glitches stopped, but Wayland has its own separate issues. However, for the sake of a stable Emacs, I'm using Wayland on my laptop for now.
>>108690853>emacs fontWorks on my machine.Sounds like a skill issue OP
