On Tue, May 25, 2010 at 4:53 PM, Bee <beeyaw...@gmail.com> wrote:
> On May 25, 1:19 pm, Tony Mechelynck <antoine.mechely...@gmail.com>
> wrote:
>> On 25/05/10 18:03, Bee wrote:
>> > Is this a bug? Seems inoremap is not working here.
>>
>> I recommend
>>
>> :set timeout timeoutlen=5000 ttimeoutlen=100
>>
>> (or similar), where
>>
>> - both times are in milliseconds
>>
>> - 'timeoutlen' should be longer than the longest time between keystrokes
>> when you're hesitating about which key to type next in a multikey {lhs}
>> for a mapping
>>
>> - 'ttimeoutlen' should be shorter than the shortest time between
>> keystrokes at your fastest typing speed but longer than the (longest)
>> time between successive bytes sent to you by the keyboard for a single key.
>>
>> When bytes arrive with a shorter interval between them than
>> 'ttimeoutlen' milliseconds, Vim will then accept them as a multibyte
>> keycode (if found in the current termcap) in preference to a mapping.
>>
>> See the corresponding help topics for details.
>
> Hi Tony
>
> I tried what you suggested and it had no effect, tried other values,
> still get the A, B, C, D.
>
> Also tried with:
> vim -N -i NONE -u NONE
>
> Still getting:
> The arrow keys up, down, right, left produce A, B, C, D respectively.
Yes, this is a known vim bug that has been reported multiple times -
at least once by me.
~Matt
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
