especially if you never start it ;)
#neovim
https://mastodon.social/@lobsters/114298718100491384
@alisynthesis I mean, since you don’t seem to have any strong moral objections to using proprietary software, you could also consider paying for the thing you have been using for years and that seem to be happy with?
I just noticed that #neovim put out a new version that looks quite exciting. I'm one of those people that gave up on neovim with how hard it was to get it working well with LSP servers, so I started using helix instead for its better out-of-the-box behaviors. But it looks like neovim has done a lot of work to improve LSP support. https://gpanders.com/blog/whats-new-in-neovim-0-11/
I guess the upside of no one else’s figuring out how to get GraphQL playing nice with #Neovim is I’ll get to learn how treesitter and LSP work 
Anyway good morning fedi
Git reset, by accident.
10 hours of work, gone.
Learning git the hard way, yay 
At least I managed to restore some of it thanks to Neovim's undo history 
I mean, I don't necessarily *want* to dump #vscode in favor of #neovim, but vscode uses so much memory and cpu, especially with remote or #container #development. But here I am, learning how to configure neovim. I guess I'm learning #lua too. #programming #ide
Sigh, I think I might have to switch away from #VisusalStudioCode. Seems the only stuff they work on is #AI, to the detriment of everything else.
Shall I move back to #vim? Or rather #neovim. Do I still have the patience to configure that just the way I like it?
I could also try out that newfangled #zed editor that is getting all the hype these days.
One must-have feature is it having good vim keybindings though, I'm lost without them.
#SoftwareDevelopment #golang #rustlang #rust
Dude I love the fact that this quote from Bram Moolenaar is included on the neovim.io website:
>"A nice looking website, that’s one thing Neovim did right." —Bram Moolenaar
This is both sarcastic and a nice tribute to Bram.
I’m liking #HelixEditor more and more each day. I think it has a ways to go; and I’m not nearly as fast in Helix as I am in Vim (mostly because I keep stopping to look stuff up) but I see no reason, with _my_ workflow, not to use Helix as my daily driver. (This after more than 20 years as a #Vim and then #NeoVim user). The LSP and tree-sitter stuff are absolutely compelling.
If you are constantly SSHing into machines you don’t control; and that’s your whole job — you probably have a different answer.
This week's tech topic of interest has been Neovim.
I started with Emacs, but in my work as a Linux sysadmin Vim is always available, so I've learned what I need to get around.
Lately Neovim has been coming up as an alternative to tools like vscode, so I started exploring. I've watched a few videos by TJ DeVries and been jumping into the terminal.
Neovim certainly makes me appreciate Vim more. Unfortunately, you're not going to see nvim on work servers - just vanilla vim.
#neovim
Neovim 0.11 came with built-in support for auto completion from language servers. And it has a new structure for configuring the language servers. It’s a really nice addition. It’s still missing some things the completion plugins provide. But there’s something really nice about not relying on plugins for everything. So for now, I try working without them. #neovim #editor #lsp
Oh, joy! Another #GitHub plugin to make your #Neovim experience even more convoluted 
. Because who wouldn't want to blend #Python testing with existential dread? Let's automate the chaos! 
https://github.com/richardhapb/pytest.nvim #Automation #Chaos #ExistentialDread #HackerNews #ngated
I have to _blame_ @willmcgugan for rediscovering the power of the 
His amazing work with #Rich and #Textual for 
got me to realize how much has happened since GUI and mouse took over the world.
This year it all begins to come together to form a good base with #ArchLinux 
#Ghostty 
#Tmux and #Neovim 
to really get going with.
If I knew beforehand, what a nest of
- I would have done it years ago 
