On Fri, Sep 11, 2009 at 06:57, Matt Wozniski m...@drexel.edu wrote:
On Thu, Sep 10, 2009 at 4:13 AM, John Beckett wrote:
Aleafs wrote:
:1,$ s/\t0\n/\n/g
Note that :% is a shortcut for :1,$
In a substitute, \n means two different things:
- In the pattern, it refers to a newline.
On Sunday 13 September 2009 20:56:17 Bram Moolenaar wrote:
I won't look at patches that add new code without knowing your full
name. It's a copyright thing. Politeness too.
Awww, of course. It ended up being this address because failure to be able post
to vim.org (and
not to
On Sunday 13 September 2009 20:56:17 Bram Moolenaar wrote:
I won't look at patches that add new code without knowing your full
name. It's a copyright thing. Politeness too.
Awww, of course. It ended up being this address because failure to be able
post to vim.org (and
not to
Bot Hiestand wrote:
On Thu, Sep 3, 2009 at 6:13 AM, Bram Moolenaarb...@moolenaar.net
wrote:
Here's a probably better patch, and a test case to show the behavior I
expect from exists() with respect to autocommands:
Thanks for the patch and testcase script. Would you be
Milan Vancura wrote:
thank you for the answer.
The main reason is Vi compatibility.
So what about an option changing this behaviour (causing all movements
throwing
an error if they can't be done) and add that option to be a part of what
'compatible' sets?
The reasoning is that
Milan Vancura wrote:
:help Space says that all 'l', 'space' and 'right' are
equivalent. This is not true for vim (:set nocompatible) as the
default value of 'whichwrap' option for vim (b,s) makes difference
between 'l', 'Right' and 'Space' at end of lines.
Same for 'h', 'Left' and 'BS'.
Hi Bram,I am developing a collaborative plain text editor, and that would be
a collaborative Vim. Several people can edit the same file concurrently.
That would be very exciting, right?
To serve this purpose, I need a way of communication from my process to Vim.
I know that we can use OLE
