On Sep 11, 1:08 am, Tony Mechelynck [EMAIL PROTECTED]
wrote:
On 10/09/08 22:59, Szabolcs Horvát wrote:
2008/9/10 Szabolcs[EMAIL PROTECTED]:
It turns out that I was wrong. Vim *can* open these files if I use
the :e command, or I browse to the file with Vim as you suggested, or
I just
In gvim 7.2 (on Windows Vista, using the default colorscheme), I found
a syntax highlighting bug. I commented out a block of PHP using the
HTML comment tags of !-- and --. But the PHP code was not grayed
out as it is in other editors (like Topstyle).
table width=100% cellpadding=2 trtd
!--
Hi
Valgrind memory checker finds a memory leak in Vim-7.2.15.
The steps to reproduce are a bit too messy to describe here
and I have not been able to find a simple way to reproduce it.
However I can reproduce it 100% of the time:
==1182== 150 bytes in 2 blocks are definitely lost in loss record
On 11/09/08 11:18, Szabolcs wrote:
On Sep 11, 1:08 am, Tony Mechelynck[EMAIL PROTECTED]
wrote:
On 10/09/08 22:59, Szabolcs Horvát wrote:
2008/9/10 Szabolcs[EMAIL PROTECTED]:
It turns out that I was wrong. Vim *can* open these files if I use
the :e command, or I browse to the file with
kkruecke schrieb:
In gvim 7.2 (on Windows Vista, using the default colorscheme), I found
a syntax highlighting bug. I commented out a block of PHP using the
HTML comment tags of !-- and --. But the PHP code was not grayed
out as it is in other editors (like Topstyle).
Sure this is a bug?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 04, 2008 at 10:09:07PM +0200, Bram Moolenaar wrote:
Tyler Spivey wrote:
hello. I have noticed that starting from 7.1.329, using vim in the
console with the encoding set
to utf8, there is a bug with redrawing characters.
The
kkruecke wrote:
In gvim 7.2 (on Windows Vista, using the default colorscheme), I found
a syntax highlighting bug. I commented out a block of PHP using the
HTML comment tags of !-- and --. But the PHP code was not grayed
out as it is in other editors (like Topstyle).
table width=100%
