I've opened an issue over at their repository, so once that gets added we could add back support for notepad++.
notepad-plus-plus/notepad-plus-plus#9680

Releasing the example file to cargo create additionnal un-necessary steps when one want to package the library for a linux distribution. It also increase the size of the crate for no reason.

Hi 👋 thanks for creating this crate. I'm planning on using it in a project of mine. I would love if there was a way to specify the extension (or suffix) of the temporary file that is created when you call edit::edit. This would be useful because then syntax highlighting would work on the opened file.

I was imagining a basic API like

edit::edit_with_suffix(text, "toml")

or

edit::edit_with_extension(text, "toml")

Hi, thanks for this library. I've been trying it on a Mac and I've noticed that it works perfectly for terminal editors like vim, nano, or pico, but not for graphical editors like Sublime Text or VS Code.

For graphical editors, I find it opens the correct editor but the opened file is blank. Also, it returns the original, unaltered text to the terminal immediately without waiting for the editor to close.

I've seen this same behaviour with Sublime Text, VS Code, and Atom.

(Running the edit 0.1.2 test binary on macOS Catalina.)

Thanks.

The nature of this crate is basicly just spawning and waiting, an optional async API would be a benefit for some usecases here^^

I'm working on a GUI application, and was hoping to be able to use this crate to allow users to edit some files. However, it seems to be attempting to launch my CLI editor (nvim) despite being launched from a GUI, which unfortunately makes this crate unusable as it is now.