Say I have a buffer like the following:
★
Say that I then select and copy that character. I then get:
★★
Say that I then copy it again (i.e., pressing middle-button twice
inside the xterm):
★★#
Why does that happen?
nikolai
Hello.
In Make_mvc.make there is such a sequence of characters that is
understood ok by make but, because of a rough syntax definition, vim
treats this sequence as a start of a character literal and highlights
half of the file as a string. Fixing this issue inside syntax
definition is not
Ilya Bobir wrote:
In Make_mvc.make there is such a sequence of characters that is
understood ok by make but, because of a rough syntax definition, vim
treats this sequence as a start of a character literal and highlights
half of the file as a string. Fixing this issue inside syntax
Ilya Bobir wrote:
As it was discussed earlier, on MS VC++ 2005 additional defines is
required in order to use some of the standard C library functions
without warnings. This defines should be done before inclusion of a
windows.h header. This defines was added into vim.h. In if_ole.cpp
On Sat, Jun 24, 2006 at 12:36:42PM +0200, Nikolai Weibull wrote:
Say I have a buffer like the following:
★
Say that I then select and copy that character. I then get:
★★
Say that I then copy it again (i.e., pressing middle-button twice
inside the xterm):
★★#
Why does that
In message [EMAIL PROTECTED] of Sat, 24 Jun
2006 13:53:35 in , Bram Moolenaar [EMAIL PROTECTED] writes
Ilya Bobir wrote:
In Make_mvc.make there is such a sequence of characters that is
understood ok by make but, because of a rough syntax definition, vim
treats this sequence as a start of a