Improve "No Editor" error

[elwayman02]

ERROR release-it-lerna-changelog configured to launch your editor but no editor was found (tried $EDITOR and searching $PATH for editor).

This error could be improved by telling the user that the release-it config specifies that we launch your $EDITOR. The user may not have been the one to set up the release-it config for that repo, so they may not understand why they're getting this error other than the missing $EDITOR token.

[rwjblue]

I wonder if instead of making the error better we could just prompt with a selection of detected editors? There are some decent npm packages that we could leverage for that, and it seems better still than an even better error message.

What do you think?

[elwayman02]

I like this, with the caveat that it would be even nicer if the prompt gave them an option to select a detected editor or no editor at all. That way, the owner of a repo could set launchEditor to true, but a co-maintainer could also choose not to use an editor if that's their preferred workflow. Nothing would change about the existing workflow of auto-opening if $EDITOR is set, but we should account for the possibility that the user has purposefully left it un-set.

[rwjblue]

an option to select a detected editor or no editor at all.

Ya, sounds great! I really like that direction. I personally always want the ability to manually review and tweak the lerna-changelog results one last time (hence wanting to use launchEditor), but this proposed workflow is a really nice fallback for when $EDITOR is missing that still mostly provides the same capability (we will most likely find an editor on every system) and a simple painless opt-out without failing the release process.

[elwayman02]

My editor is my IDE, can you detect that? :P