Bram Moolenaar wrote:
[...]
The second was a proposal to represent floats as numbers with decimal
points but no additional punctuation which was implicit in this report
from Ilya Bobir:
- I did a search for vim scripts that use concatenation operation
between two numbers without
Philippe Fremy wrote:
Ilya Bobir wrote:
Philippe Fremy wrote:
[...]
For sending key strokes to Vim or for evaluating functions in Vim, you must
use the|clientserver|interface.
use the |clientserver| interface.
When shown in the help file, the | is not visible
Philippe Fremy wrote:
[...]
For sending key strokes to Vim or for evaluating functions in Vim, you must
use the|clientserver|interface.
use the |clientserver| interface.
[...]
kind first item example ~
Command bufID:name!seqno
Adri Verhoef wrote:
[...]
Now do:
:se fileencoding=utf8 bomb
[...]
Note, that you probably do not want to use BOM with UTF-8.
See http://unicode.org/faq/utf_bom.html#29 (Q: Can a UTF-8 data stream
contain the BOM character (in UTF-8 form)? If yes, then can I still
assume the
Bram Moolenaar wrote:
[...]
I would still like feedback on the format of floating point numbers:
123.456
1.23e-3
I did a search for vim scripts that use concatenation operation between two
numbers without interleaving space. It appears that Google Code Search was
able to
Lin wrote:
Hi all,
[...]
To let the syntax checker see the buffer, I think the solution can
only be making copies of related files The Flymake plug-in for
Emacs, as already referred to in the first post, seems to be running
some reasonable heuristics on finding the related files. But
Mike Williams wrote:
Hi
[...]
Yep, I submitted a patch along these lines. Unfortunately, I still
don't think it's a solution. I still managed to end up with a rogue
sticky command prompt. This was on XP SP2 so using GetConsoleWindow() -
looks like a bug in Windows where the message
