Edit in Neovim

by Theseus
5
4
3
2
1
Score: 56/100

Description

Category: Coding & Technical Tools

The Edit in Neovim plugin offers a seamless integration between Obsidian and Neovim. With this plugin, when you open a file in Obsidian, it will automatically pop up in Neovim as well, allowing you to edit the file directly within the external editor of your choice. This means that you can take advantage of Neovim's powerful features and customizations while still enjoying the benefits of Obsidian's note-taking capabilities.

Reviews

No reviews yet.

Stats

31
stars
6,951
downloads
9
forks
678
days
46
days
46
days
14
total PRs
1
open PRs
3
closed PRs
10
merged PRs
18
total issues
3
open issues
15
closed issues
44
commits

Latest Version

a month ago

Changelog

What's Changed

  • chore(deps-dev): bump esbuild from 0.17.3 to 0.25.0
  • chore(deps-dev): bump minimatch from 3.1.2 to 3.1.5
  • chore(deps-dev): bump flatted from 3.3.1 to 3.4.2

README file from

Github

Edit in Neovim

For those who love the power of Obsidian, but just can't shake wanting absolutely any and all text editing to happen inside of neovim.

Important

Several users have reported that the plugin doesn't function when obsidian is installed using flatpak.

What does it do?

This plugin will pop open a new terminal and runs neovim inside it (You can turn this off in the settings) when Obsidian starts up.

After that, every time you open a file inside of Obsidian, that same file will get opened as a new buffer (or focused if already open) inside of the listening neovim instance. This effectively gives you the "linked tabs" functionality you would get inside Obsidian, but with an external editor (in this case neovim) instead.

Why?

I know Obsidian has vim bindings, but I've built up my own Neovim config and customised it to my liking and that's where I like to edit text.

Have new Neovim buffers open in Obsidian

If you also want new buffers in Neovim to open up in Obsidian, here's what you'll need:

These should work out of the box. But there is a bug that occurs when files are being renamed or deleted from within obsidian while the corresponding buffer is open in neovim; resulting in infinite loops. It's recommend to do file operations from within neovim while using the plugin.

Edge Cases

There's alot of different terminals, systems, and just ways to install neovim. As such there's a good chance there's a few cases where this plugin doesn't work as I'd hope it would, or where you need to handle things alil differently. Below is a non-exhaustive lists containing the ones I've seen so far:

  • When using Ghostty on MacOS, set the terminal path to: /Applications/Ghostty.app/Contents/MacOS/ghostty.