Description of problem: The vim-minimal package no longer depends on vim-common. This causes terminal emulation problems when using vim. Particularly with arrow keys. When you enter insert mode via i or A and try and use the arrow keys on your keyboard instead of moving the cursor A, B, C, and D, characters are inserted along with new lines and the like. If I remember my ANSI BBS days the ANSI character codes for arrow keys are ESC[A, ESC[C et al. It appears VIM is not interpreting these ANSI codes correctly. Is this functionality dependant on the contents of vim-common? It certainly appears so as I installed the package and the problems go away. Version-Release number of selected component (if applicable): 6.2.457-1 How reproducible: Always. Steps to Reproduce: 1. Install vim-minimal. 2. run vi test.txt enter instert mode and use one of the arrow keys. Actual results: Escape codes are inserted into the buffer. Expected results: The cursor should move. Additional info: Fedora Core 1 vim-common dependencies: [oliver] luna:~$ rpm -e vim-common error: Failed dependencies: vim-common is needed by (installed) vim-enhanced-6.2.121-1 vim-common is needed by (installed) vim-minimal-6.2.121-1 vim-common is needed by (installed) vim-X11-6.2.121-1 Fedora Core 2 vim-common dependencies: [oliver] atlas:~$ rpm -e vim-common error: Failed dependencies: vim-common is needed by (installed) vim-enhanced-6.2.457-1 vim-common is needed by (installed) vim-X11-6.2.457-1 Note vim-minimal is not listed (but it is installed). Now this might have been intentional on the part of the Fedora Core packagers. Maybe they wanted vim-minimal to be very minimal and not include a lot of the extra guff from vim-common. However they have practically erradicated the usefulness of vi as an editor for those of us who can't remember the k,l,j etc movement keys. Please revert to the old rpm dependencies. Either that or package at least some basic terminal emulation support with vim-minimal. Thanks
*** This bug has been marked as a duplicate of 123205 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.