med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

358
active users

#neovim

8 posts8 participants2 posts today

Created a Neovim :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: codeberg.org/Larvitz/nvim-ansi 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 :-)

#nvim#neovim#vim

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 (github.com/nvim-lua/kickstart.) 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!

#Vim#Neovim#Coding

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.

herecomesthemoon.net/2025/06/i

MOND←TECH MAGAZINE · I really like the Helix editor.‘Search & Replace’ popup windows are bad user interface design.

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