Currently if you run vroom it tries to invoke vim classic as 'vim', or if you pass the --neovim option it tries to invoke neovim as 'nvim'. This gets annoying in a few ways:
- It gets very confused for users who alias vim to neovim on their systems
- It gives you no way to override the vim/nvim command to run
- In error scenarios it gives really cryptic error output since it can't infer any context about how the target vim instance is supposed to work
It would be nice to generalize that and add inference so that you have more control over which vim executable it's invoking and it can more automagically figure out which options to pass to whichever vim variant it's pointed at.
Currently if you run vroom it tries to invoke vim classic as 'vim', or if you pass the
--neovimoption it tries to invoke neovim as 'nvim'. This gets annoying in a few ways:It would be nice to generalize that and add inference so that you have more control over which vim executable it's invoking and it can more automagically figure out which options to pass to whichever vim variant it's pointed at.