home.social

#neovim — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #neovim, aggregated by home.social.

  1. What’s New in Neovim 0.13 (still under development): native multiple cursors, better support for persistent remote sessions, filesystem-watcher-based autoread, structured concurrency for Lua, improvements to built-in LSP completion... #Neovim dotfiles.substack.com/p/whats-

  2. Когда есть минутка пишу г*вно код на python

    #Linux #development #neovim #kde

  3. How to use multiple Cursors, merged into Neovim nightly, scheduled for release in Neovim 0.13 #Neovim blog.olimorris.com/2026/09/02/

  4. Finally got around to setting up #neovim to render man pages. It’s trivial to get the default going, but if you’ve got the keyboard shortcuts for less burned into your mind and demand a non-cluttered view, some tweaks are required. I've captured my configs. Tested in #FreeBSD, #AlpineLinux, #macOS, and #Debian.

    markmcb.com/cli/neovim-man-pag

  5. Finally got around to setting up to render man pages. It’s trivial to get the default going, but if you’ve got the keyboard shortcuts for less burned into your mind and demand a non-cluttered view, some tweaks are required. I've captured my configs. Tested in , , , and .

    markmcb.com/cli/neovim-man-pag

  6. #neovim Development News

    The 0.12 version updates `:delmarks` command to trigger the `MarkSet` event (with `line` and `col` set to 0).

    PR:
    - github.com/neovim/neovi...

    feat(events): trigger MarkSet ...

  7. Note to self: Do NOT allow LazyVim to install a shitload of breaking changes when the kids have school tomorrow, even if you're not really intending to work tonight.

    #neovim #LazyVim #BreakingChanges

  8. What a world we live in! I noticed a post by @bremner linking to neovim fighting against removing a DHH quote. Given that DHH actively associates himself with white supremacy and ethnic cleansing, choosing to associate your project with him is quite a choice.

    Well. Reading to the end of the thread, the maintainer decided to go out with a bang. I'm not sure this is any better a look than fighting for the DHH quote in the first place, but here we are.

    Here's the link to the issue:

    github.com/neovim/neovim.githu

    Here's the patch that was finally accepted:

    github.com/neovim/neovim.githu

    And here's a link to something to use instead of Neovim:

    codeberg.org/evi-editor

    #neovim #dhh #fascism

  9. Lost in a large codebase? 🔎

    I built tgrep.nvim to bring Microsoft’s tgrep search into Neovim, with the fff-plus picker.

    • Search as you type
    • Preview matches before opening
    • Jump into splits or tabs
    • Send matches to quickfix
    • Use an index, with filesystem fallback

    Try :Tgrep in your project. I’d love to hear what would make it fit your workflow.

    github.com/vinitkumar/tgrep.nvim

  10. 🚨 New Blog Post Alert! 🚨

    My latest blog post is again about the intersection of the Java and NixOS ecosystems. This time I wrote a derivation that packages the jfmt formatter as a statically linked binary using GraalVM for use as a formatter in Neovim. It also includes some tips for debugging non-reproducible derivations.

    👉 Full Story: britter.dev/blog/2026/05/06/jf
    📄 Code: github.com/britter/nix-configu

    #nixos #java #graalvm #neovim #nixvim

  11. I really hate using VS Code for... well, anything, really.

    Thing is, I haven't yet worked out how to set up #NeoVim and #clangd for #PlatformIO and #Arduino projects. I'm guessing the Pico SDK is going to be equally as awkward when I get around to it.

    Plus, there's no way to get clangd to properly interpret Psion's old 16-bit DOS-influenced C. If LLVM can't compile it, clangd doesn't seem to care about it.

  12. Does anyone have any tips on using #clangd with the #Arduino libraries? Specifically for use in #NeoVim.

    At some point I'll move this project over to the Pico SDK, but for now I'd like to edit this code without resorting to VS Code.

    #AskFedi #LazyWeb #hivemind

  13. Other projects I use every day:
    #Matrix spec & clients like #FluffyChat and #nheko
    #Bitwarden & #Vaultwarden password manager
    #Neovim text editor
    #clangd LSP

    I'd love to encourage these projects to jump ship, and I celebrate those that do. I am much more likely to provide quality contributions if you host on your own forge, or a free one, and I am sure I'm not alone in this.

    GitHub is hostile to FOSS and, despite giving away lots of free-of-cost stuff I believe ultimately hurts us.

  14. @pythno #clangd is a LSP for c language and c++. So, if you don't install clangd it'll not work.

    #neovim

  15. @pythno Try ...
    1. Install #clangd but don't setup LSP. This will disable auto completions.
    2. Use #codelldb for debugging -> igorlfs.github.io/neovim-cpp-d

    #neovim

  16. I'm now convinced that I'm not going to be able to get #clangd to behave properly with C89 code for 8086.

    It might be a skill issue on my part, but there's only so much time I want to spend getting my tooling working.

    Until I have a better solution, I'll have to stick with VS Code.

    #retrocomputing #retrodev #NeoVim

  17. Is anyone out there using #NeoVim for #retrodev in C, specifically 16-bit x86 (e.g. DOS)?

    Do you also have a working language server?

    I'm hitting some snags trying to configure #clangd that I just don't have with VS Code. (e.g. recognising cdecl)

    Also willing to hear from people using other editors!

    EDIT: This is actually for Psion EPOC16 development, but the TopSpeed C compiler runs in DOS and uses DOS conventions to make 8086 binaries. The Psion SIBO C SDK then strips the MZ header and adds an EPOC16 one.

    #retrocomputing #msdos

  18. My next #NeoVim related challenge is to work out how to get #clangd to work with the #Psion SIBO C SDK.

    It's probably going to involve #cmake, something I've successfully avoided for some time now.

    Needs must, as they say.

  19. Is anyone using #NeoVim with #clangd for #retrodev with early-90s C libraries? I can't make head nor tail of the documentation.

    So far for my .clangd file I've got something like this:

    CompileFlags:
    Add:
    "-I/home/alex/dosbox/sibo-c/SIBOSDK/include"

    But I don't think this is actually doing the job of setting the path, not to mention ignoring all other (more modern) include paths. I also need to set C89 and maybe tell it that it needs treat the code as something vaguely DOS-like.

    What's really galling is that this is very easy with VS Code and just bloody works -- one JSON file that it practically fills in for you and you're done.

    EDIT: To clarify, the build environment is inside DOSBox (TopSpeed C compiler, Psion SIBO C SDK), so I don't think tools like bear will work (though I'm happy to be proved wrong!).

    EDIT 2: Fixed the path in the code snippet (which I changed originally for essentially no reason).

    #retrocomputing #clang #llvm

  20. Convention over customization.
    This is why I love projects like Keep a Changelog, Conventional Commits and Semantic Versioning. They allow for some neat processing by other tools which just wouldn't ever be possible if everyone did their own, custom thing.

  21. y claro que he hecho #EditorHopping !

    comencé con el bloc de notas por allá del 2004 cuando aprendí html, luego llegué a usar #DreamWeaver y #FrontPage hasta que tomé Java en la prepa y conocí #NetBeans que me acompañó un buen rato. Al migrar a linux usé #gedit pero pasé más tiempo en #Geany que es una joyita. Luego estuve largo tiempo en #SublimeText hasta que me decidí a saltar a #vim en 2014 y luego #neovim, que me acompaña desde ~2019

  22. Hi diddly-dee,
    It's #LazyVim for me!

    Swapped my very basic config with LazyVim and I'm very happy!

    Next steps are:
    - Easy swapping of LSP (mainly #clangd) configs so that I can switch between targeted platforms (e.g. Windows and Linux, or Arduino UNO and RP2040)
    - Integration with #PlatformIO
    - Some way to side-by-side compare and modify git untracked changes

    These are all things I have in VSCode, the target changing being the most important. I hope that there are equivalents for #NeoVim!