Neovim, e/plugins

Posts refer to Nvim 0.13 (dev build).

Discuss usage/config/ideas at:

[Neovim, e/plugins @Neovim]

Plugin authors: ":help dev-test-plugin"[1] describes how to use Nvim's own test framework in your repo/CI, using a small Makefile.

Further work is planned[2] where the end goal is to ship the test framework with Nvim itself.

[1] https://t.co/6SFwZqyhRN
[2] https://t.co/SebgiSQutK

[Neovim, e/plugins @Neovim]

@_buf It will find any session that can be reached from the machine you are running it from, i.e. any session whose pipes live in stdpath('run').

If you ssh into a tmux session, any Nvim running in the remote tmux can see sessions from other Nvims on that remote machine.

[Neovim, e/plugins @Neovim]

Try ":FzfLua serverlist" if you use fzf-lua https://t.co/MwdSMp7W0E . It lists (and previews) all running Nvim sessions (+ remote sessions, if their local sockets live in stdpath('run')).

It also shows a "last activity" column (Nvim 0.13 "v:useractive").

[Takuya 🐾 devaslife @inkdrop_app]

New video🎬 Effective Neovim setup for agentic coding towards 2027
@Neovim @AnthropicAI

[Neovim, e/plugins @Neovim]

@urisan oops, *whoosh*

it was funny in both cases though 😂

[Neovim, e/plugins @Neovim]

Nvim 0.13 includes vim.uri.parse() and vim.Uri.

Designed to fit editor UX, and builds on the pros/cons of vscode's Uri impl (and node.js, etc).
- removes ambiguity for LSP, plugins, etc.
- future: all stdlib functions (vim.xx) to accept vim.Uri (optionally) instead of plain strings.

https://t.co/s88ae7l1O8

[Neovim, e/plugins @Neovim]

@urisan not sure what to make of that comment

[Neovim, e/plugins @Neovim]

This is just an API for parsing/representing URIs.

Remote ssh support is tracked in https://t.co/FhBmFDrzv7 and linked issues.

We're making incremental steps in that direction (e.g. :connect support), but the "feel local" topic is quite big and we don't have a clear story there.

[Neovim, e/plugins @Neovim]

@LMartini28763 https://t.co/irqD3I3cwj

[Neovim, e/plugins @Neovim]

@LMartini28763 soon

[Neovim, e/plugins @Neovim]

This is the way. 🤩

[almonk @almonk]

the creativity and pace of the community has been astounding. my favourite so far is `neorex`, a plugin for neovim which gives it Rex-native splits and floating windows.
https://t.co/b8Xh1jFIlr

[Neovim, e/plugins @Neovim]

@furiousape @tachy0n_z @neo_subhamoy with CmdAtom (Nvim 0.13), you can repeat any mapping/command/etc, which reduces the need for many shortcuts/aliases.

[Neovim, e/plugins @Neovim]

@LMartini28763 soon

[Neovim, e/plugins @Neovim]

Text 'wrap' in Nvim 0.13 is "conceal-aware".

Supported for extmark-driven conceal (treesitter, etc.), not "legacy" conceal (matchadd(), :syntax).

[Neovim, e/plugins @Neovim]

@facundoduhau Do you mean Progress as opposed to LspProgress? https://t.co/IDRMM8tz6r

Note that LSP "progress" can be quite noisy, so this wouldn't be enabled by default. ":help LspProgress" shows how to enable it currently. https://t.co/7gLHDUsR6P

[Neovim, e/plugins @Neovim]

If :edit or :write is slow (on a very big file), Nvim 0.13 will emit progress events.

[Neovim, e/plugins @Neovim]

@peter_p_c it's planned! https://t.co/YGrE8swUvb

[Neovim, e/plugins @Neovim]

More :help pages are in "flow" layout.
https://t.co/baizJAnda8

Besides nicer HTML rendering, this opens the door for a future "presentation mode" where hard-wrapped text blocks can be viewed in flow layout.

[Neovim, e/plugins @Neovim]

Neovim :help docs in PDF form (autogenerated):
https://t.co/CBMcn8yPpJ

Also, tables are now rendered in HTML/PDF (and :help has basic highlighting for table headings).

[Neovim, e/plugins @Neovim]

@riskirills 2027

[Neovim, e/plugins @Neovim]

Nvim 0.12.6 release

https://t.co/f39vPKOHR5

[Neovim, e/plugins @Neovim]

@LMartini28763 in ~2 weeks