Hide Forgot
Description of problem: mapping of vim-commands to special function keys not possible e.g. :map <S-F2> a123<esc><cr> doesn't work although accepted and verified by command :map but : :map <S-F5> a123<esc><cr> works as expected (appends string "123" at current position) behaviour seems to depend on environment : differs in graphics mode with Gnome from behaviour in console.screen (Environment TERM=xterm vice Term=linux) Version-Release number of selected component (if applicable): Fedora 16 vim 7.3.315 How reproducible: Install Fedora 16 with German language pack (Standard installation + some additional packages). Start Gnome Terminal, start vim in terminal with any file and try the key mappings described above Steps to Reproduce: 1. log in 2. start terminal 3. start vim with any file 4. map <S-F2> a123<esc><cr> 5. press key Shift-F2 Actual results: vim enters insert mode and inserts string "1;2Q" Expected results: vim enters insert mode and inserts string "123" Additional info: independ of the commands assigned to the key Shift-F2, vim will always enter insert mode and display "1;2Q", which seems to be assigned to the function key by the environment. This is the same string as displayed when pressing Shift-F2 at the bash-prompt. So the new mapping is ignored in vim.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.