Bram Moolenaar wrote:
> I suspect that for some reason the "need_mouse_correct" flag is set when it
> shouldn't. I can't reproduce the problem, thus it's hard to find.
>
...
> If you can run Vim in a debugger, you could also put a breakpoint at the
> code you deleted and find out where it's c
On Wed, 2009-10-28 at 22:06 +0100, Bram Moolenaar wrote:
>
> I'm not sure how useful it is to show something instead of a space.
> Isn't it obvious that there is a space when there is nothing?
Bram, I can't speak for the author, but I'd like this feature to make
it easy to visualize:
* other no
On 28-10-2009 Bram Moolenaar wrote:
>
> Lech Lorens wrote:
>
> > It is possible to scroll down (i.e. CTRL-Y in normal mode) an empty
> > buffer if it is being compared with another buffer consisting of at
> > least two lines. This means it is possible for the cursor to appear
> > "outside of th
Dominique Pelle wrote:
> Valgrind memory checker detects use of freed memory in the
> Motif GUI version of Vim-7.2.267:
>
> [...]
>
> Bug can be reproduced as follows:
> - Compile Vim with Motif or lessTif.
> - Run gvim with valgrind:
> $ cd vim7/src
> $ valgrind ./vim -f -g 2> valgrin
Jérémie Roquet wrote:
> I've just started to use Vim, and missed the possibility to display
> middle-dots (or any other visible character) instead of spaces, so I
> made the following patch.
> It adds "space" in the allowed "listchars" arguments.
>
> Just in case someone find this useful ; I fo
Lech Lorens wrote:
> The attached patch fixes a problem with syntax-based folding. Steps to
> reproduce:
> - make sure that you have folding for comments in C source code enabled:
> : if exists("c_no_comment_fold")
> :unlet c_no_comment_fold
> : endif
>
> - with the following settings:
>
Lech Lorens wrote:
> It is possible to scroll down (i.e. CTRL-Y in normal mode) an empty
> buffer if it is being compared with another buffer consisting of at
> least two lines. This means it is possible for the cursor to appear
> "outside of the file" - on nonexistent lines.
>
> To reproduce t
>> 4. foldmethod=all seems buggy. When I turn it on, folds open even
>> when I move through them vertically, and never fold even when I try to
>> close them explicitly. Setting all the documented foldopen values
>> doesn't have this affect, so evidently 'all' is not the same as
>> including ever
Lincoln Ramsay wrote:
> Hello all,
>
> I noticed that gvim was warping my pointer unexpectedly and as this was
> annoying, I thought I'd try to track it down.
>
> It turns out gvim was behaving 'correctly' - exactly as described in the
> :mousefocus preference. The thing is though that I do
Evan Laforge wrote:
> I hope this is the right place to post this, I couldn't find any bug
> tracker. I searched in the archives a little but didn't find these
> mentioned, but they have been bugging me for years and years so it may
> have been mentioned long ago... sorry if these are repeats.
I would like to post the following attached patch to the MAXIMA syntax file,
so someone being responsible for such things can apply it.
Andre
-- Forwarded Message --
Subject: VIM syntax file for MAXIMA
Date: Tuesday 27 October 2009
From: andre maute
To: Robert Dodier
Dear R
Hi Yakov
On 28 Okt, 07:47, Yakov Lerner wrote:
> On Wed, Oct 28, 2009 at 00:52, Yakov Lerner wrote:
> > PS
> > I learned once that on win32, you *must* write
> > if(sock == -1) and never if(sock < 0).
> > Win32 sockets can be negative. Yes they really can be.
> > msdn specs _open() as returni
12 matches
Mail list logo
