Hello,
It would be nice to have a robust mouse tracking in vim when running in a
terminal emulator window wider than 223 character cells.
The maximum reported mouse coordinates is limited to 223 due to protocol
limitation (XTerm Control Sequences,
http://invisible-island.net/xterm/ctlseqs/ctlseqs
Reply to message «Why does ':normal' ignore the 'count' prefix for mapped
keys?»,
sent 08:00:58 06 January 2011, Thursday
by Douglas A. Augusto:
It looks like a bug and so must be forwarded to vim-dev mailing list. By the
way, everything works with feedkeys:
vim -u NONE -c 'redir! > messag
Bram Moolenaar wrote:
Dennis Benzinger wrote:
Am 29.12.2010 18:41, schrieb Roy Jamison:
Hi all,
A bug has been reported to Launchpad (quite a while back in fact) at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/137854 and also to
Debian at http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
On 06-Jan-2011 11:37, ZyX wrote:
> Reply to message «Why does ':normal' ignore the 'count' prefix for mapped
> keys?»,
> sent 08:00:58 06 January 2011, Thursday
> by Douglas A. Augusto:
>
> It looks like a bug and so must be forwarded to vim-dev mailing list. By the
> way, everything works with
Hi All, I found an problem with omni completion.
net-snmp has 3 structs like
1)
typedef struct XTable_data_s {
u_long z;
} XTable_data;
2)
typedef XTable_data XTable_undo_data;
3)
typedef struct XTable_rowreq_ctx_s {
/** this must be first for container compare
Ingo Karkat wrote:
> On 06-Jan-2011 11:37, ZyX wrote:
> > Reply to message «Why does ':normal' ignore the 'count' prefix for mapped
> > keys?»,
> > sent 08:00:58 06 January 2011, Thursday
> > by Douglas A. Augusto:
> >
> > It looks like a bug and so must be forwarded to vim-dev mailing list. B
Hello,
Consider the following _vimrc (for Windows vim 7.3)
set nocompatible
set lines=47
set cmdheight=2
set number
Open a file
Add the pattern "foobar" at lines 10 and 70
Go to top
1/ Normal mode
Type / foobar (foobar at line 10 is found)
Type n (foobar at line 70 is found)
Type n (foobar a
On 06-Jan-2011 17:30, Bram Moolenaar wrote:
>
> Ingo Karkat wrote:
>
>> I encountered this, too, and it severely impacts automated testing of
>> Vim plugins. (I was hit by this recently, sorry that I didn't yet
>> report it; I'm glad that the example mapping from Douglas shows the
>> problem so s
On Jan 6, 4:13 pm, Ingo Karkat wrote:
> Wow, I hoped it would be simple, but I didn't imagine it THAT simple :-) Any
> insights whether the implementation of passing FALSE was deliberate?
>
> I can at least confirm that this patch fixes the issue in my automated tests.
> I
> will run through my
Yukihiro Nakadaira wrote:
> > Dennis Benzinger wrote:
> >
> >> Am 29.12.2010 18:41, schrieb Roy Jamison:
> >>> Hi all,
> >>>
> >>> A bug has been reported to Launchpad (quite a while back in fact) at
> >>> https://bugs.launchpad.net/ubuntu/+source/vim/+bug/137854 and also to
> >>> Debian at http:
This also occur with horizontal layout with different size (e.g.
notebook + additional monitor). And vim window is on smaller one.
+--+--+
| | |
| monitor1 | monitor2 |
| | |
+--+ |
^ +--+
|
maximized
I noticed that the problem can be reproduced with single monitor when
there is two gnome panel on top and bottom.
+--+
|xx| <- gnome panel
|++|
||||
|| vim window || <- maximized vim window
||||
|++|
|xx| <- gnome
Hello,
I happen to use :digraphs quite a lot to insert mathematical symbols
in documents.
However, finding the characters and their input sequence is *very*
straining for the eyes.
I wonder whether each of the three columns output by :dig could be
coloured to help reading?
Also, it may help *a lo
13 matches
Mail list logo
