| 2007-05-15 08:28:05 |
Micah Cowan |
vim: statusexplanation |
|
While arrow-key support doesn't bother me particularly, I'd agree that invoking "vi" should bring up a traditional (compatible) vi. However, this should probably be discussed on the ubuntu-devel-discuss list, for the correct solution if not for the desired result.
vim.tiny does what it does only because it has been specifically patched by Debian to look for /etc/vim/vimrc.tiny when and only when it has been invoked as vi. None of the other compiled variants of vim (nor, of course, upstream) have such conditional rc-checking behavior. And I'm not sure that they should: that seems like the wrong way to go.
Instead, what should possibly happen is that the "vi" alternative should be linked directly to vim.tiny by default, instead of vim. That way, installing and update-alternativing a different vim variant would leave vi still invoking a compatible session. |
|
| 2007-05-16 19:55:50 |
Micah Cowan |
vim: statusexplanation |
While arrow-key support doesn't bother me particularly, I'd agree that invoking "vi" should bring up a traditional (compatible) vi. However, this should probably be discussed on the ubuntu-devel-discuss list, for the correct solution if not for the desired result.
vim.tiny does what it does only because it has been specifically patched by Debian to look for /etc/vim/vimrc.tiny when and only when it has been invoked as vi. None of the other compiled variants of vim (nor, of course, upstream) have such conditional rc-checking behavior. And I'm not sure that they should: that seems like the wrong way to go.
Instead, what should possibly happen is that the "vi" alternative should be linked directly to vim.tiny by default, instead of vim. That way, installing and update-alternativing a different vim variant would leave vi still invoking a compatible session. |
|
|
