Guillem Ballesteros:

I have reached Vim nirvana with my latest setup. I can finally bring all the advantages of working within Jupyter to my favorite text editor. You get the code cells and interactive development with a fine-tuned editor and plain text files which can be put through linters and code formatters.

He goes on to share the plugins and config that make the nirvana happen.

So you got tired of AI just suggesting code edits, and now you want it to help you run code, too. Silly human, you have come to the right place. This will take five steps.

This gets an A+ for creativity. Fire up your shell, then launch Neovim. Then shell out with :VimShell to get back to where you started, but with Copilot suggestions.

My guess is the ergonomics of this are… bad. But a cool hack, regardless!

Bhupesh Varshney’s been using Vale (a syntax-aware prose linter) in his writing workflow and it has significantly impacted the words he chooses. Here’s how he describes the tool:

Just like when writing software we use static analysis tools to find common problems, vale aims to help writers configure what words/prose to choose while writing technical documentation.

Neovim is Bhupesh’s fav editor. In this post he walks through getting Vale all set up and running with it.

Ships with a file explorer, autocompletion, git integration, status line, fuzzy finding, and more.

This week Neovim core maintainer TJ DeVries joins Jerod and guest co-host Nick Nisi (from JS Party) to follow-up on our Vim episode with a conversation dedicated to Neovim. TJ tells us why Neovim was created in the first place, how it differs from Vim, why Lua is awesome for configuration and plugins, what LSPs are all about, the cool tech inside tree-sitter, and how he’s writing his own fuzzy file finder for Neovim called Telescope.

We had a lot of fun recording the Vim with me series alongside episode 450, so I thought, “Hey, let’s keep it going!” We have Nick Nisi for you today. Nick is a regular panelist on JS Party, co-hosted our upcoming Neovim episode of The Changelog, and is personally responsible for the #vimparty channel of Changelog’s community Slack.

(If you have any requests of people you’d like to see Vimming with me, let us know in the comments!)

NVUI looks like it’s still rough around the edges (lots of rendering/crashing issues opened over the last few days, no build instructions, etc.) but it looks pretty sweet!

I’ve been test-driving Neovim (episode coming soon!) and I’m impressed at how hacker its community is. Should use NvChad directly? I dunno, but it can surely be relied upon for inspiration and cherry-picking.

This is such a cool idea (inspired by Limelight), written in Lua, and using TreeSitter for better dimming. Will plugins like this start pulling normal Vim users over to Neovim?

Vimpeccable is a plugin for Neovim that allows you to easily replace your vimscript-based .vimrc with a lua-based one instead. Vimpeccable adds to the existing Neovim lua API by adding new lua commands to easily map keys directly to lua.

All of the power and customization of Vim without the inscrutable and othewise compulsory Vimscript? Sign me up! (metaphorically… I’m far too lazy to customize Vim anymore than I already have.)

Vim-clap is different than previous finders because it uses the new floating_win (NeoVim) and popup (Vim) interface. File lookup and switching have long been what keep me out of Vim as my daily driver (clunky UIs, slow results). Nothing beats Sublime Text in this category, in my opinion.

But this looks pretty awesome. I might have to give this a test drive and see if it wins me back.

This “Conquer[er] of Completion” is an intellisense engine for Vim 8 and Neovim which supports extension features of VS Code. I haven’t tried it yet, but the folks in our #vimparty Slack channel are pretty in to it.