I don't think I've had a worse time trying to configure something in my life. I tried to go from vim -> neovim to get the lsp, you need 20 plugins, there's 5 different plugin managers and you're stupid if you're not using the sixth that just came out 5 minutes ago. I get lazyvim which is supposed to just werk and be minimal toiling, it's like 8 different lua files spread across multiple different folders. Any option or autocommand that was like 1 line in vimrc is now its own 10 line lua function. None of the pieces of neovim/lazyvim work together well either, like the functions don't even fucking work or overwrite themselves with hardly any ways of chaining them together in the right order. Emacs has hooks for everything, this has seemingly dick all or obtuse shit.I can't even change my fucking COLORSCHEME!!! Lazyvim installs a plugin that's a theme (why does it even NEED to be a plugin??? Isn't this like a json tier expedition???) and boots it every time on launch. There is supposed to be some autocommand shit file where I COULD change it if it worked and didn't just overwrite the scheme anyway. Do I even NEED an lsp? I'm not a super smart huge programmer but the one thing I believe an LSP does is showing/autocompleting available functions and what they do, which seems like it would save a lot of time. I know it also gives me syntax warnings but honestly who cares because that breaks often and my screen is littered with bs warnings or false positives that the compiler couldn't give a fuck about. idk.Fuck lua and it's this.that.bull.shit crap. Why is everyone obsessed over fucking dots? hypr.land.wiki.fuck.you too, anything lua can kiss my ass
>>110089412You can just use the native package manager. It just works.Not sure why themes need a plugin, but i don't really care
>>110089490then you just enable all the LSPs you want and you are mostly done
>>110089412>Fuck lua and it's this.that.bull.shit crap. Why is everyone obsessed over fucking dots? hypr.land.wiki.fuck.you too, anything lua can kiss my assbased. you should just (switch-to-emacs 'op).
^ fug. didn't mean to sage.
>>110089412I shared all the same frustrations with you regarding neovim. Just take the VSCode + vim keybindings pill. People bitch about microsoft but out of the box you get an LSP + visual debugger + ONE extension/plugin manager, and it all just fucking works with 2 minutes of setup. for serious dev with minimal tinkertrooning, vscode is unmatched. You can always keep tmux + vim open on another monitor for when you want to larp. But you’ll come crawling back to daddy vscode.
>>110089412Just use vim
>>110089412>>110089842before neovim i used sublime text 2. that was in 2010s.before it was probably something like comodo edit (firefox xul based), and notepad 2 earlier, but that's learning things in late 2000s.i use neovim it daily, in a corporate setting.havent used vscode for more than like 20 minutes at once.all these electron based editors (atom, brackets, vscode) didn't feel quite right 10 years ago. coc.nvim provided same lsp features in vim/nvim early on so i used that.best of luck with your neovim setup.
>>110089503>>110089506You didn't sage anyway. To use sage properly you need to put in the options field, but you put it in the name field. Also no one uses sage anymore after moot made it invisible which was gay. It is what it is. I was going to call you a newfag but then I realized the fact that you know what sage is is proof you're not. Go figure.
>>110090160also neovim 'distros' is usually just some kid hoarding random github scripts and putting a logo on itneovim gold xp catchy omarchy edition
>>110089412>I get lazyvimyour fault you fell for the meme distro. You are supposed to just use the build in and read the docs its all there already.
>>110089842Yeah that's what I ended up on. I really like vim keybindings, and the plugin in VSCode could be better, but Neovim is just missing so many things out of the box, and it's not trivial to install what you need like in VSCode. I want to click a button and have all I want. I'm not going to spend hours ricing my Neovim setup because I have actual work to do, unlike most people here. Also VSCode just looks so much prettier than Neovim, and I value that for something that I stare at 8 to 10 hours arday.
>>110089412>still using an editorISHYGDDT
>>110090522I know. I'm embarrassed to admit to using sed
>>110089412Skill issue + works on my machine. Cope.LSPs are great and they work just fine. Your issue was using some cancer prebuilt config when you could do what you desired with a few dozen lines of config.
>>110089412go from vim to emacs evil-mode like a normal person
I went through the same things, trying to install plugin managers, watching some old outdated video because they just updated how it works, switching to lazyvim, getting overwelmed with all the bloat, etc.I figured out how to install an lsp without a plugin manager, and thats how I use it now, just vanilla nvim with the lsp. You really should avoid all the plugin crap, thats a nightmare of dependencies and things that might change and get in the way of your workflow, learn nvim itself and you'll find out most plugins are completely unnecessary. If it takes 5 seconds to open your text editor because its checking github for an update, you might as well just use vscode
>>110091433>just use vscodeor Zed, which is better than vscode and nvim, but if you'Re still into nvim keybinds etc. Zed has the best vim integration out there
>>110089412I'm just dropping this right here.
Just use Emacs like a normal white chad.
>>110089412skill issue
>>110089412calm down ma'am
Just do your own config bit by bit, don't install those retarded "distros" that you have no idea how to use with how much they add, stick to classic VimScript configs and do manual plugin installation if you need any, plugin managers are all a meme since they need an entire fucking Git instance to work.
>>110089412i used astronvim as a starter, but i agree with op that these well intentioned neovim dorks have created a special kind of hell with this config situation... but we're stuck here now
as a rule I try not to tinkertranny my editor too much because I hop between several machines and don't want to bother copying my rc files. neovim is fine with its defaults but at that point just use regular vim. if I need fancy features I throw in the towel and use some slop like vscodium>>110090169I use sage all the time to insult OP without bumping their stupid thread
>>110089412don't really care about your problems but>LSPI've gone back and forth on this, the only two features of LSP I kind of use are "go to definition" and symbol search (so you can just look at a list of all functions in your program, for example)not very necessary to be honestand yeah what this anon said >>110092909
>>110089412i've tried to migrating by simply using my vimrc and just write compatibility codeand it worked kinda, but not exactly the samefew plugins I use didn't workthere are some weird problems with history files in neovimbreaking kill ring (rotating undo) pluginbreaking gutter signs for marks, they don't appear after closing and opening the file, likely because of fucked up, non-compatible history handling in neovimanother plugins that broke are several custom motions pluginsother features I expected to work, having different behaviors, glitchingotherwise everything worked as in vimbut if it works mostly the same but with bugs I decided to not use it, because why bother if everything under vim works for me?I have a lot of custom vimL code and legacy plugins, so breaking shit annoys mei don't care about lua, nor I care about some stupid gimmicks for zoomerslsp works under vim with CoC (conqueror of completions) so the only thing neovim has over vim is treesitter syntax highlighting, and fancy gimmicks plugins
Was thinking of switching from lazyvim to vanilla neovim to get the real experience but from the looks of it imma just stick with lazyvim cuz it just werks
>>110089412Just use SI, bro.
>>110092021I already fell for the vim keystrokes bs and learned that for a year or two sell me on emacs
>>110089412>I can't even change my fucking COLORSCHEME!!! Lazyvim installs a plugin that's a themeThis is fucking real. You can still extract the .lua theme file from the repository. The devs apparently turned theme into plugins and even split the theme file across multiple files for extreme customization shit no one needs. It's fucking retarded. >>110089503>>110092021do you guys use a pedal or is the emacs pinky shit fake
skill issue
>>110089412>why does it even NEED to be a plugin???Half of the light themes are poorly maintained too so it's an even bigger pain in the ass, and the nvim devs decided fucking cyan on a light background was a good choice for the default theme so I have to care about plugins. Can't even use it out of the box.
>>110095804>do you guys use a pedal or is the emacs pinky shit fakeIt's fake. Evil mode is for redditors.
VIM still has a noticeable lag when I "ctrl+alt v shift-i" insert text on multiple lines (useful for commenting out multiple lines in one go) so I'll stick with NEOVIM
if you need LSP or something like that, then youre emacs guy - fuck off to emacs and IDEs.i would understand somebody who was initiated long AFTER neovim appearance, but transition from vim => neovim is only possible because the host is corroded with updooot ideology
>>110091992But that's a fork anon
>>110096967set ttimeoutlen=5
>>110089412I have a ~120 line config I kept in vimscript, no lsp server, no plugins and I just use the vanilla features it comes with OOTB. quickfix list for errors and grep output through makeprg and grepprg, netrw for file nav, built in C syntax highlighting and native ctags integration for tag jumping. :terminal has replaced tmux for me and the only feature I’ve missed is an alignment toolI program like a caveman and I think it’s just better that way. these rapidly changing lua plugins are like a house of cards, constantly breaking or becoming unmaintained where you have to play musical chairs with the next thing, so fuck ‘em
>>110097322I get wanting to program like a caveman but bare bones tmux gives you so much that vim terminal doesn’t.
>>110097358it’s just easier to manage windows and panes from within vim itself rather than have to juggle how vim handles it with how tmux does. I haven’t really missed tmux but I also don’t really need more than two vertical panes with either a vim buffer or a terminal on the right and then an occasional quickfix pane across the bottom. this workflow is just not really easy with tmux
>>110097358>terminalGNUnix terminal is more retarded than windoze conhost (that supports key ups btw, but theres no software that fully utilize that afaik), so no keyboard cowboy would use terminal-based vim or editor, it simply doesnt support 2 keys pressed simultaneously. only a GUI based vim may be used proficeintly.
