Lmst

Linda tarde de domingo para pasármela en la PC aprendiendo a hacer un blog con #gohugo y #neovim y tomando unos 🧉

Sobre gustos (dijo una vieja...)

My Neovim Config — Opinionated, Minimal, and Actually Usable

I've written up a how-to for using arf and {terminalgraphics} in R.nvim. Glad I did. I discovered a few gotchas that I'd forgotten and now have them recorded and cleaned up my nvim config files at the same time.

So, now you can have the IDE console experience in R.nvim AND the graphics baked in, no X11 or {httpgd} windows to fuss with. The only catch is you have to use Kitty or Wezterm for your terminal emulator.

https://adamhsparks.netlify.app/2026/03/10/further-enhancing-r-nvim-with-arf-and-terminalgraphics/ cc @jimbob

#RStats #Neovim #RNvim

@ahnlak @neil you mean #neovim+#NvChad or #icevim?

https://www.youtube.com/watch?v=c4OyfL5o7DU

🖥️ After years of VS Code I switched to Neovim – on an old MacBook Pro running Linux Mint.

The trigger was pretty simple: VS Code was just too heavy for the hardware. CPU at 100% on startup, Firefox open at the same time? Forget it.

Honestly the switch wasn't as big as expected – I had always used the Vim plugin in VS Code for shortcuts anyway. Moving to native Neovim was more of a "finally going all in" moment.

💡 What surprised me most: the performance. Neovim starts in milliseconds, the fan stays quiet, and the whole system just feels more relaxed.

I'm still experimenting and gradually porting the features I loved in VS Code. Debugging, CMake integration, AI support – there's still a lot to explore.

Anyone made a similar switch or have plugin recommendations for C++ development?

#Neovim #VSCode #Linux #CppDevelopment #LinuxMint #DeveloperTools

Currently compiling #Neovim inside a build of a custom ROS 2 jazzy Docker image.

Optimal Docker usage right here...

RE: https://hgaza.masto.host/@omer/116228969909639315

People have the choice:

- They can say that dealing with "politics" is a waste of time and they'd rather be productive.
- They can show a genocide victim some empathy and receive answers like this.

At the end of 2026, when people will share their "Spotify Wrapped" again and "reflect back on their year", they can write in their diary that they listened to 52 audiobooks this year at 2x speed.

I will have a folder on my computer with screenshots of messages of love like this one.

No matter whether I'll be 40, 50, 60, 70, or 80 years old and look back on those screenshots, I will feel so much more than any of these "productive" folks who can't remember the plot of a single audiobook they listened to at 2x speed.

#ToxicProductivity #BuildInPublic #python #rust #swift #swiftUI #golang #rustlang #NixOS #arch #neovim

“A Guide to vim.pack (Neovim built-in plugin manager)”
“A somewhat concise yet comprehensive guide to vim.pack: how it works and how to use it.”
https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack

#Vim #Neovim #Lua

"""
Sorry old dear
"""
--- me, as to emacs, upon having finally bothered to redo the Wanderland integration that's been solely neovim's responsibility for the last month or two

===

"""
Welcome home
"""
--- she, as to I

===

It just feels more solid to use, no idea why... evil gives me the same buttons

#emacs #neovim #wanderland

simple facade to integrate wanderland's tools into my publishing workflow

@thomasfuchs

Pah, the #AtariFalcon030 was absolutely superior!!!

#letsReviveAncientFlamewars

And #emacs is a decent, but bloated OS, that still lacks a reasonable text editor. They should actually port #NeoVim to it at last.

;-)

я наманкипатчил решение :D

#nvim #neovim #typst #treesitter

$```diff diff --git a/runtime/lua/vim/treesitter/query.lua b/runtime/lua/vim/treesitter/query.lua index cd217e6ab2..ba384c17ca 100644 --- a/runtime/lua/vim/treesitter/query.lua +++ b/runtime/lua/vim/treesitter/query.lua @@ -625,13 +625,22 @@ predicate_handlers['any-vim-match?'] = predicate_handlers['any-match?'] -- (match, pattern, bufnr, predicate, metadata) ---@type table<string,TSDirective> local directive_handlers = { - ['set!'] = function(_, _, _, pred, metadata) + ['set!'] = function(match, _, bufnr, pred, metadata) if #pred >= 3 and type(pred[2]) == 'number' then -- (#set! @capture key value) - local capture_id, key, value = pred[2], pred[3], pred[4] + local capture_id, key, value, value_2 = pred[2], pred[3], pred[4], pred[5] if not metadata[capture_id] then metadata[capture_id] = {} end + if value_2 then + if type(value) == "number" then + value = vim.treesitter.get_node_text(match[value][1], bufnr, { metadata = metadata[value] }) or "" + end + if type(value_2) == "number" then + value_2 = vim.treesitter.get_node_text(match[value_2][1], bufnr, { metadata = metadata[value_2] }) or "" + end + value = value .. value_2 + end metadata[capture_id][key] = value else -- (#set! key value) ```$

OpenBSD support for arm64 architecture also added in blink-cmp Neovim plugin (completion plugin with a fast fuzzy matcher written in Rust): add GitHub workflow to build binary on OpenBSD/arm64 and support in Lua code #OpenBSD #Neovim https://github.com/saghen/blink.cmp/pull/2441

Updated my #tmux config so that inactive panes have a different background color.

Why didn't I think about that earlier? Makes such a huge difference!

(Just like adding a different background color for insert mode stopped me from getting totally confused any time I use #neovim )

I figured out that #vim introduced #aislop code in their repo and actually #neovim team seems don't have problem to merge this kind of code.

For me is unfortunally, but it something that is happening.

I'm not ready to migrate all my way to #code and my way to work, becauase my #neovim setup makes me proud. Long time ago I started to work with vim/neovim so I have them deep in my mind.

Nevetheless I think I should start to learn alternatives, maybe #emacs

@mrmasterkeyboard @xinit I did add #evi to the @OS1337 package wishlist in lieu of #neovim...

I'm learning Tidal Cycles, and it turns out it's pretty easy to get cool J Dilla-style microtiming effects:

#TidalCycles #Algorave #LiveCoding #SuperCollider #Neovim

#neovim Development News The 0.12 version will allow setting 'fsync' option per buffer, instead of only global. This can be useful when writing to a slow filesystem. PR (Vim patch): - github.com/neovim/neovi...

vim-patch:9.1.2024: 'fsync' op...

OpenBSD support added for blink-cmp Neovim plugin (completion plugin with a fast fuzzy matcher written in Rust): add GitHub workflow to build binary on OpenBSD/amd64 and support in Lua code #OpenBSD #Neovim https://github.com/saghen/blink.cmp/pull/2423

I've started writing my own SuperCollider synths to use in Tidal Cycles! This one is a classic acid bass, and I'm using it for the bassline from “365”

#TidalCycles #SuperCollider #Algorave #Acid #ElectronicMusic #Neovim

Ugh, someone just told me that both #vim and #neovim are now slopcoded. I genuinely need to stop using computers ever again.

#neoVIM

Client Info