On Tuesday, March 26, 2013 8:30:48 PM UTC+9, Bram Moolenaar wrote:
eagletmt wrote:
I found that Vim cannot be compiled with --enable-rubyinterp=dynamic
on 64bit platform if the Ruby's version is 2.0.0. I attached a patch
to fix it. Please check it.
Thanks. I hope a few
Let me explain a bit more...
What I am trying to do is to make vim into an *special file* editing program
with revision control.
I have added several elements, which if I can complete I will provide a diff
patch for, that are working fine.
At this stage I am trying to complete an integration
Hi glts!
On Mi, 27 Mär 2013, glts wrote:
In Operator-pending mode it is possible to use Ex commands to move the
cursor. When editing the command-line in this situation, Esc normally
aborts the whole operation. For example, in normal mode:
d:callEsc
This command has no effect.
But
Christian, thanks for looking into this.
On Wed, Mar 27, 2013 at 4:01 PM, Christian Brabandt cbli...@256bit.org wrote:
On Mi, 27 Mär 2013, glts wrote:
d:callEsc
This command has no effect.
But it doesn't really abort.
I don't understand. The command is cancelled silently, just as it is
On Wed, March 27, 2013 17:18, glts wrote:
Christian, thanks for looking into this.
On Wed, Mar 27, 2013 at 4:01 PM, Christian Brabandt cbli...@256bit.org
wrote:
On Mi, 27 Mär 2013, glts wrote:
d:callEsc
This command has no effect.
But it doesn't really abort.
I don't understand.
On Wednesday, March 27, 2013 7:03:15 AM UTC-5, Paul Moore wrote:
Something odd is happening for me on Windows 7 (64 bit). I have my own
compiled copy of Vim, and when I run
:%!sparkup
I get Shell returned 1 and the buffer is empty. Here, sparkup(.py) is a
Python file - I have a .py
I still don't think it should be an error. Sometimes when you start
typing d3... you realize you wanted change instead of delete, so
you press Esc and start again.
For me, d:call Esc is the same thing. Perhaps you want to use a
custom function but you forgot to source the relevant file, so you
Hi glts!
On Mi, 27 Mär 2013, glts wrote:
I still don't think it should be an error. Sometimes when you start
typing d3... you realize you wanted change instead of delete, so
you press Esc and start again.
For me, d:call Esc is the same thing. Perhaps you want to use a
custom function but
Christian,
On Wed, Mar 27, 2013 at 11:01 PM, Christian Brabandt cbli...@256bit.org wrote:
Ok, what do you think of this updated patch?
Won't there be a redundant call to clearop() now when cancelling
ordinary Ex commands? I suppose it should work though. Thanks.
Personally, I'd rather not
