Ohhhhhhhhhhhhhh #neovim finally get its native plugin manager: https://github.com/neovim/neovim/pull/34009
Now I can’t wait for 0.12

Ohhhhhhhhhhhhhh #neovim finally get its native plugin manager: https://github.com/neovim/neovim/pull/34009
Now I can’t wait for 0.12
An interesting post by a #vim purist :-)
"why I got rid of all my #neovim plugins"
https://yobibyte.github.io/vim.html
It's been a long time, but it's #FollowFriday time!
#MechanicalKeyboards
@keyboards
@emory
@andy_warb
@abcdw
@arthurzenika
@MoskitoHero
#pkm #notes
@thelinuxcast
@PhoenixSerenity
@denis
@matt
@jdheyburn
#photography
@hexamanganite
@jeffhug
@shojiwax.com
#FountainPens #ink
@vividfoundry
@toga
@paradoxmo
@Parker51
@Dianora
@peterk
@JulesJones
@keraba
@inkycicada
Boosts appreciated
Created a Neovim configuration for writing Ansible playbooks/roles/collections. With linting, auto-completion, highlighting of blocks, indentation, git integration and nice UI.
If someone is interested, I put it on my Codeberg here: https://codeberg.org/Larvitz/nvim-ansible together with a README.md, that explains keybindings, installation instructions etc.
It's also good for Python software development and contains the LSP definitions for that as well. But the primary goal, was to create an Ansible development environment with all bells and whistles :-)
I've been more and more dissatisfied with the GUI text editor options, and I finally know enough about Neovim to have a setup that covers most of what I liked about e.g., VSCode!
I used the Kickstart (https://github.com/nvim-lua/kickstart.nvim) config files. So far, I just changed the theme back to default, and the rest of the settings worked for me.
I wanted something where I could at least have
- A small terminal split at the bottom
- An easy-to-use file browser (here, netrw and the “Telescope” fuzzy search)
- Easy extensibility (Neovim does both VimScript and Lua plugins, and I have the “Lazy” package manager for those)
Very happy with it!
I've been using the #HelixEditor as my daily driver for the better part of a year now and I couldn't be more happy with it. I've managed to get a near-IDE setup and experience thanks to zellij and some awesome TUI tools.
This article aligns well with my experience, I recommend reading it if you're "modal editor curious" or dissatisfied with your (neo)vim config maintenance burden.
it looks like developers cannot be productive without an AI code assistant, well I honestly have to say that #copilot has been useful for boilerplate specs but code... mixed feelings. More, most of the tools are for #vscode which I honestly don't like. I prefer my #neovim setup and folks, remember the #enshittification of the Internet, once you're locked in, corporations can do whatever they want of you... #generativeAI #developers #programming
A small issue with my #Neovim spelling
#blog #100DaysToOffload : 067/100
Neovim tip for today
When you are in command-line mode or inside the search input, you can hit the `<C-f>` to enter edit mode to have access to all your regular text editing tools. It opens the command-line history, the same one that you can access via `q:`.
I have a #Python file that does not have a *.py extension. I would like to tell my #NeoVim that it is a Python script, so that it can do proper syntax highlighting.
I know that I achieve this by adding some special comments to the file, that are interpreted by NeoVim. But I don't remember how to do it and how the feature is called.
All the involved terms are bad for asking Google. Can somebody give me a hint please?
I’ll rewrite my #Neovim status line because that’s who I am, and I wonder what do you think *should* be there. I think I’ll remove the line and column numbers and left only the buffer name, warnings, errors and window number
Sure, I got that sentiment. But your original post was a bit misleading:
"I got Ruby/CSS/JavaScript LSPs working with #NeoVim and so can you..."
You should've mentioned docker right away :P
A potentially interesting method of applying spellchecking suggestions -- use Ctrl+Q in normal mode to cycle through them: https://gist.github.com/Konfekt/9f141a8e21a864d43181dbb712b4ea90
Wow, seems overly complicated.
kickstart.nvim is a great starting point for a general #NeoVim setup (LSP setup included).
It's one file and has a lot of comments and explanations included.
Lazy.nvim is more complete, but more opinionated. There are other frameworks out there as well.
@davetron5000 having struggled (multiple times) to setup ruby-lsp in #neovim on macOS directly, seeing your post title that adds docker to the mix triggered outright schadenfruede. i had to read immediately. much respect . bookmarked for future me bored with things running too smoothly
I got Ruby/CSS/JavaScript LSPs working with #NeoVim and so can you:
If you often work with large JSON or YAML files, this Neovim plugin might be able to help you out with navigation: https://github.com/JFryy/keytrail.nvim