On 9/27/06, Meino Christian Cramer <[EMAIL PROTECTED]> wrote:
From: "Yakov Lerner" <[EMAIL PROTECTED]> Subject: Re: Meta/Alt-confusion and no end Date: Wed, 27 Sep 2006 13:18:06 +0000> On 9/27/06, Yakov Lerner <[EMAIL PROTECTED]> wrote: > > On 9/27/06, Meino Christian Cramer <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > As VIM insists on getting Meta/Alt-keys as binary codes and not as a > > > ESC-<key>-combination I tried first to revert the rest of my > > > environment, which handles ESC-<key>-combinations well to what vim > > > exspects. zsh and mrxvt have option to switch between both (would a > > > solution for vim, too!). The Midnight Commander insists of getting > > > ESC-<key>-combinations. > > > > > > So I reverted everything back to the previous state (using > > > <ESC>-key-combinations) and inserted: > > > > > > let c='a' > > > while c != 'z' > > > exec "set <M-".toupper(c).">=\e".c > > > exec "imap \e".c." <M-".toupper(c).">" > > > let c = nr2char(1+char2nr(c)) > > > endw > > > > > > in the top of my ~/.vimrc. > > > > > > NOW F1 did the same as > > > > > > 1~ > > > > Looks like F1-F4 conflict with <M-O>. Try to avoid using > > <M-O>, and remove mapping <ESC>O (:iunmap <Esc>O). > > > > This is quick workaround. There must be better solution > > that allows to use F1-F4 together with <M-O> but it will take > > time to figure. The problem is that F1-F4 generate > > seauences that begin with <Esc>O > > Looking at this again, I don't understand why the confusion. > F1 generates ^[OP (nb uppercase O), whereas imap from this tip > (tip#738) map ^[o (lowercase o). So I don't understand what causes > the confusion. Does your F1 generate ^[OP as mine ? > > Yakov > Hi Yakov, thanks for your reply ! :) using i_Ctrl-k it produces [11~ with my console vim (or better a gvim called as vim). So its a little different than yours. What OS you are using ?
Linux Fedora FC5, Konsole. Yakov
