Show HN: Yode-Nvim – Focused Code Editing for Neovim

An off-topic comment:<p>Interesting for the “GIF” section to have links to .mp4 videos — the “GIF” word now seems to be synonymous to short playable animations. Love that the author did that though, I’ve seen too many repos with multiple giant (~10MB) GIFs on the README and burn my mobile data plan.

Hey this is super cool, but can it work without the floating windows? Can I assign seditors to regular vim splits (am I using the terminology correctly?).<p>The narrow functions in Emacs were great, and almost made me switch to Emacs. I know NrrwRgn exists, but it didn&#x27;t automatically sync the buffers, so you couldn&#x27;t have them open side by side. This looks better, but I don&#x27;t like the automatic layout stuff. I prefer to control that myself.

What’s the advantage of this over creating splits and navigating to the relevant code? This is what I do all the time, having a hard time understanding how this would improve that.

This looks <i>amazing</i>, I love the idea.<p>I wonder, as a general feeling, does the implementation of the floating narrowed regions involve a lot of hacks&#x2F;workarounds, or does it come fairly naturally to nvim?

This looks great, nicely done! I didn’t know I needed this :)<p>Does anyone know if this exists for Emacs? I use both nvim and Emacs but primarily Emacs and would love to have this on both.

I have been using NrrwRgn[0] for editing and presenting individual sections of code. How does Yode compare?<p>[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;chrisbra&#x2F;NrrwRgn" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;chrisbra&#x2F;NrrwRgn</a>

This looks really cool. Will absolutely try it out. :)

How does Yode compare with tree-sitter?