RE: Unsubscrible vim_dev

2010-05-05 Fir de Conversatie Simson Liu
I have subscrible the list with new gmail box. But I can't unsubscrible the list with my current work mail box. I have sent the vim-dev-unsubscr...@vim.org the empty mail message many times, but have no any effect. So other managers don't have to look, I have done the

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

2010-05-05 Fir de Conversatie Mosh
On Tue, May 4, 2010 at 3:59 AM, Chris Sutcliffe ir0nh...@gmail.com wrote: On 4 May 2010 00:23, Patrick Texier wrote: On Mon, 3 May 2010 13:23:48 -0700, Mosh wrote: No more problems, it works on window32 bit (XP with VC60) and linux 64 bits gcc, ones I tested on. I'm waiting a patch for

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Matt Wozniski
On Tue, May 4, 2010 at 8:14 PM, Tom Sorensen wrote: On Tue, May 4, 2010 at 7:14 PM, Paul LeoNerd Evans leon...@leonerd.org.uk wrote: Over the past 7 years, I have been a member of the #vim channel on Freenode. Almost every week we get somebody in the channel who wonders such things as how to

RE: Unsubscrible vim_dev

2010-05-05 Fir de Conversatie John Beckett
Simson Liu wrote: I can still receive mail from the list. I have tried again, and have responded directly to Simson. I'm just replying here to let others know that I have acted. John -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Henrik Öhman
On May 5, 1:14 am, Paul LeoNerd Evans leon...@leonerd.org.uk wrote: Vim's keyboard input system revolves centrally around a queue of bytes. This worked well when all the world was serial terminals. In this new world of GUIs this model doesn't work so well. I advocate changing it to a queue of

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Ben Fritz
On May 4, 6:14 pm, Paul LeoNerd Evans leon...@leonerd.org.uk wrote: Vim's keyboard input system revolves centrally around a queue of bytes. This worked well when all the world was serial terminals. In this new world of GUIs this model doesn't work so well. I advocate changing it to a queue

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Dennis Benzinger
Original-Nachricht Datum: Wed, 5 May 2010 00:14:06 +0100 Von: Paul LeoNerd Evans leon...@leonerd.org.uk An: vim_dev@googlegroups.com Betreff: Keyboard input handling Vim's keyboard input system revolves centrally around a queue of bytes. This worked well when all the world

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Matt Wozniski
On Wed, May 5, 2010 at 11:20 AM, Ben Fritz wrote: On May 4, 6:14 pm, Paul LeoNerd Evans leon...@leonerd.org.uk wrote: Vim's keyboard input system revolves centrally around a queue of bytes. This worked well when all the world was serial terminals. In this new world of GUIs this model doesn't

Re: Keyboard input handling

2010-05-05 Fir de Conversatie Bram Moolenaar
Paul LeoNerd Evans wrote: Vim's keyboard input system revolves centrally around a queue of bytes. This worked well when all the world was serial terminals. In this new world of GUIs this model doesn't work so well. I advocate changing it to a queue of keypress events. Over the past 7

inputdialog with lots of text expands past window boundaries

2010-05-05 Fir de Conversatie David Fishburn
Vim 7.2.411 Windows 7 64bit Windows XP SP3 Both have nVidia cards (though different). I also have my TaskBar at the TOP of my screen since I extend my monitor above my laptop. The TaskBar is also 2 rows deep. This introduces some additional undesirable behaviour. I am issuing an inputdialog

Possible bug when side scrolling

2010-05-05 Fir de Conversatie John Beckett
In the following, these Unicode characters are used: \u200e = 'LEFT-TO-RIGHT MARK' (U+200E) \u2013 = 'EN DASH' (U+2013) On my 7.2.411 system, the following commands show a bug: gvim -u NONE :set columns=96 nowrap encoding=utf-8 :$put =repeat('a',50) . nr2char(0x200e) . repeat('b',40) .