Closed jbelmont closed 11 years ago
I can't reproduce this. Try running Vim with the following command from delimitMate's repo dir:
vim -N -u test/_setup.vim
and see if you can reproduce it. You'll need to enable filetype, syntax, etc. by hand.
I ran this command and was not able to reproduce the behavior but with this command I was not
able to have syntax highlighting or delimitMate enabled. It just appeared that vim was loaded with no plugins at all.
One comment I would like to make is that I noticed that in css that this behavior was flaky at best because I did have times that other css elements such as:
a {
text-decoration: underline;
color: Black; // :exec "normal!
Reopen this issue if you find out what's causing it or find it too disrupting of your workflow.
Thanks!
I have let delimitMate_jump_expansion = 1 turned on my vimrc and this happens only when I on a css file. For instance on a css definition like so:
How can I prevent this from happening. For now how I go about solving this is by just pressing a space before I jump to next curly brace, and then it jumps to right curly brace no problem, but if I don't press a space then I get this output everytime.
Note that I do not get this output on definitions such as these on a css files.
these definitions work fine.