I think new highlight groups (Spell*, Pmenu*, etc) should be
listed somewhere in version7.txt. Not all colorschemes support
new vim features ant it's unclear for users how to change color
of that ugly magenta square. The point is to list all new
groups in one place with links do detailed
Georg Dahn wrote:
I tried, also on Windows XP, but I don't see the problem. I have no
idea why it happens for you. Must be something obscure. What
compiler did you use? Does it also show in the distributed Vim 7.0g?
That's interesting. I use the same compiler as you (at least
Hari Krishna Dara wrote:
Using Vim 70g, I am seeing a weird problem with CursorMoved autocommand.
In a function, I am removing my CursorMoved autocommand, moving the
cursor and adding the CursorMoved autocommand back, but the cursor
movement somehow ends up triggering the autocommand. At
Hi!
I tried several versions, starting with gvim -u NONE -N
and still don't see the problem. I have no idea what
could make it appear.
It would be interesting, what is common between Mikolaj Machowski and
me, since we both can see the problem. I am working on two computers
and this problem
Bram,
I use vim sessions a lot. I use the .vse extension and have them
associated with 'gvim.exe -c source %1' so I can double click on
them. It's nice when they start up without requiring an enter to
continue. However there were two I started up today that both
required me to hit
On 5/5/06, Edward L. Fox [EMAIL PROTECTED] wrote:
Hi VIMmers,
I'm sorry that I'm not able to sync the SVN repository with the CVS
repository on time today, because the network is suffering some
problems. I had tried different routes but all failed. Maybe there is
something wrong with the main
Alexey Froloff wrote:
I think new highlight groups (Spell*, Pmenu*, etc) should be
listed somewhere in version7.txt. Not all colorschemes support
new vim features ant it's unclear for users how to change color
of that ugly magenta square. The point is to list all new
groups in one place
This is formatted as a script that you can cut run.
The - indicates the output of the 'echo' command.
Ignore comments at the beginning of the line, they are there
only to prevent useless errors.
-- [script start]
let a = [[1,2], [3,4]]
echo a
- [[1,2], [3,4]]
This works
Zdenek Sekera wrote:
This is formatted as a script that you can cut run.
The - indicates the output of the 'echo' command.
Ignore comments at the beginning of the line, they are there
only to prevent useless errors.
-- [script start]
let a = [[1,2], [3,4]]
echo a
-
I am beginning to understand a bit more but
not quite all yet:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
[...]
echo list a=a
- list a= [[1,2], [3,4]]
This works, but why? Isn't this also concatenation of
two strings?
Note: it adds a blank after
I have this problem (trivially simplified a real case):
let a=a\nb\nc
When echo'ing it, it displays lines:
:echo a
a
b
c
Now I need to call system() and have the contents of 'a'
as the file, without actually writing the 'a' into a temp file,
something like this:
execute system(. editor . .
Hi Zdenek,
On 5/5/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
I have this problem (trivially simplified a real case):
let a=a\nb\nc
When echo'ing it, it displays lines:
:echo a
a
b
c
Now I need to call system() and have the contents of 'a'
as the file, without actually writing the 'a' into a
I don't know if it's supported to do this, but I'm crashing VIm70g,
WinXP by doing a new in a TabEnter autocommand. The crash doesn't
immediately follow the new command, but soon after when other
functions start looking through the windows.
I can't get a crash in a test case, but if you run the
BTW, I can't get WinDbg to recognize the .pdb files, although I've set
the Symbol path to the directory containing them. Is there some trick
to this?
14 matches
Mail list logo
