On Sun, Sep 29, 2019 at 10:42 PM James McCoy <[email protected]> wrote: > While I understand the frustration you experienced, I don't think adding > such a script is an appropriate solution. I don't think there's much to > do from the perspective of this package. Possibly, there's an > opportunity for enhancing the command-not-found package, but that would > be a separate investigation/discussion.
Thank you for your reply! I hear you. My hunch is that enhancing command-not-found wouldn't be an ideal solution either. This is for two reasons: A) Experienced users might not pay much attention to command-not-found's output. B) The command-not-found script runs kind of slowly, so users in a hurry might even interrupt it with Ctrl+C. Therefore: Perhaps it would make sense for vim-tiny to provide a /usr/bin/vim symlink which points to the vim.tiny binary? A minimal Vim is already installed; you might as well let users run it using the "vim" command. :) If not: Why would adding a /usr/bin/vim script, which outputs some help text and then quits with exit code 1, be a less-than-ideal solution? Cheers, --Jason
