#neovim Development News
The 0.12 version will add experimental `nvim__exec_lua_fast()` function to allow remote API clients to execute code while Neovim is blocking for input.
PR:
- github.com/neovim/neovi...
feat(api): add experimental nv...
#neovim Development News
The 0.12 version will add experimental `nvim__exec_lua_fast()` function to allow remote API clients to execute code while Neovim is blocking for input.
PR:
- github.com/neovim/neovi...
feat(api): add experimental nv...
Dogfood ain't dogfood if you buy it from the shops...
We're going to build the UI by building the UI, starting with the editor
HTML, YAML, Markdown - whatevs, they're all trees
Trees and web components is all a girl needs
[and a preview button]
#devops #devopsendgamewithallthepeaceandnoneofthedevops #engineering #wanderland #neovim
Hello Neovim users, can you help me?
Every now and then, when I'm simply typing in insert mode, I get a desktop notification about wl-clipboard, and can't resume typing until I press Control+C (and i) or click the notification.
Neovim 0.11.6 on ptyxis terminal, in Wayland GNOME, with wl-clipboard installed, on Debian testing. I guess the relevant configuration is:
vim.opt.clipboard = "unnamedplus"
:boostsPorFavor:
I've been fiddling around with #neovim the past couple of days. Wanted to learn how to make a plugin, so I put together something https://codeberg.org/jmstaley/mark-window
It doesn't do much, pops up a window listing all current buffer marks. Then lets you jump to one. It's not fully featured or probably even useful but it was fun learning. I would like to make it properly installable next I think
i used kmonad to give myself home row mod keys but the problem is i can no longer scroll up/down/left/right in #neovim so i guess it's time i trained myself to use ctrl-D and ctrl-U like a pro
Almost 🪿
h2 -> h2 should cut a new section my dear
Next pass though. Otherwise, how lovely is that
Getting there...
That outline view is lovely, and telescope gives me a built in preview for larger documents
===
Debugging a universe is infinitely simpler than debugging code... it's all in one place
Poke created the contents, but I need to get it to rescan for new section markers.
===
"""
fucking cool though
"""
--- me, happy shit is fucking cool
"""
that's pretty fucking cool
"""
--- me, just now
===
"""
ooh, who just poked me?
"""
--- that section, just now, upon being poked by neovim
Awe... she had twins :)
Hello there.
I really, really wanted to like emacs
I mostly just really, really liked org-mode
Sorry dude, it was evil-mode anyways, you were just a container
===
"""
welp
"""
--- me out for beers with emacs, suddenly putting my hands on my knees
===
So neovim has tree-sitter integrated huh?
Fucking remark can't just settle down with her and have some sort of baby like thing that might make things easy?
No?
I'll do that then
+++
"""
it's friday, you ain't got not job, and you ain't got shit to do
"""
--- me now, on friday, with no job and shit to do.
===
"""
fuck it, we'll build then
"""
--- the flea to the elephant, upon reaching the river
When I worked on #offpunk 2.0, I divided the code into the netcache, ansicat and openk components, hoping someone would, one day, use them to do something I never imagined.
Well, it happened: there’s now a #neovim plugin using Openk to render gemini/web pages in you #vim editor!
https://git.thatit.be/neopunk.nvim.git/
The whole story:
gemini://thatit.be/2026-02-19-21-26-12.gmi
(yes, it is a #geminiprotocol link, #gemini is a protocol, not a Google bot!)
@alina personally I can also recommend good #CLI tools that just work.
And many more.
Development on an #Immutable distro sucks. #Toolbox looks so much like an unelegant solution, with random tools polluting the host systems' .bashrc file and home directory when installing new development environments.
i want to write a blog post on configuring neovim using vimscript. but i want know how much dark magic i'm allow to use. if i show you this example config, do you think is fine?
https://gist.github.com/VonHeikemen/fc7aa25941fd34b045512ba2fb633fc9