| 2006-09-29 13:54:40 |
Trey Ethridge |
bug |
|
|
added bug |
| 2006-10-20 11:23:32 |
Andreas Simon |
vim: status |
Unconfirmed |
Confirmed |
|
| 2006-10-20 11:23:32 |
Andreas Simon |
vim: statusexplanation |
|
|
|
| 2006-11-06 12:10:12 |
Constantine Evans |
vim: status |
Confirmed |
Rejected |
|
| 2006-11-06 12:10:12 |
Constantine Evans |
vim: statusexplanation |
|
Thank you for your report, but this is actually the intended behaviour of the vi command. When invoking vim-tiny, the variant of vim installed by default, using the vi command, it reads /etc/vim/vimrc.tiny, which sets the compatible mode, so that vi acts like the original vi. The broken arrow keys are part of that compatibility. In reality, the bug is that in Dapper, the arrow keys aren't incorrectly mapped when running vi.
To run vim, instead of vi, use the vim command, which reads /etc/vim/vimrc. |
|
| 2006-11-06 14:30:23 |
IbeeX |
vim: status |
Rejected |
Needs Info |
|
| 2006-11-06 14:30:23 |
IbeeX |
vim: statusexplanation |
Thank you for your report, but this is actually the intended behaviour of the vi command. When invoking vim-tiny, the variant of vim installed by default, using the vi command, it reads /etc/vim/vimrc.tiny, which sets the compatible mode, so that vi acts like the original vi. The broken arrow keys are part of that compatibility. In reality, the bug is that in Dapper, the arrow keys aren't incorrectly mapped when running vi.
To run vim, instead of vi, use the vim command, which reads /etc/vim/vimrc. |
|
|
| 2006-11-06 23:47:04 |
Constantine Evans |
vim: status |
Needs Info |
Rejected |
|
| 2006-11-06 23:47:04 |
Constantine Evans |
vim: statusexplanation |
|
Nicolò, the arrow keys aren't mapped because compatibility mode acts exactly like the original vi, down to bugs if I recall correctly.
For this bug, I can understand the desire to have vi start vim. However, if someone wants to start vim, they need to run vim. One wouldn't use the command emacs and expect xemacs to start by default, would they?
IbeeX, a power user will not know how to fix this, because it is not easy to fix. It breaks the -v option to vim as well as breaking the vi command. The only way to fix it right now means setting compatible in vimrc, which then prevents them from running vim in nocompatible mode without changing the vimrc.
Finally, this isn't a bug - all documentation for vim states that vi and vim -v start vim in compatibility mode and read vimrc.tiny. What you are requesting is a change in the behaviour of vim, which, according to https://wiki.ubuntu.com/Bugs/CommonTasks, should go to the appropriate mailing list instead of being discussed on launchpad. But do note that I have discussed this ubuntu-devel before, and was told by several people that vi should start vim in compatibility mode (I wanted vi to start vim at the time). Perhaps with more people, you will have more success. |
|
