Could anyone explain why does Vim still have vi-compatibility mode? Why
would one use it?
As a consequence, we have to keep set nocompatible in our .vimrc; there is
much noise in docs like {not in Vi}, {Vi: no ++opt}, etc.
and I can't really understand why developers keep it so carefully.
--
2014-04-06 23:09 GMT+04:00 Bram Moolenaar b...@moolenaar.net:
Ben Fritz wrote:
On Sunday, April 6, 2014 6:42:35 AM UTC-5, Bram Moolenaar wrote:
The problem is that there will not be a standard way how to apply those
two changes. If it's just two inserts after another it would be
2014-04-04 16:04 GMT+04:00 Christian Brabandt cbli...@256bit.org:
On Do, 03 Apr 2014, Dmitry Frank wrote:
Consider a simple example: say, I just typed foo, then pressed Left key,
and typed bar. Now I have fobaro.
When I press . key, only bar part is repeated, and the same is with undo
2014-03-30 12:51 GMT+04:00 Nikolay Pavlov zyx@gmail.com:
On Mar 30, 2014 4:19 AM, Dmitry Frank dimon.fr...@gmail.com wrote:
Then, how can I get the symbol index (not byte offset) of a match?
There is awesome plugin PreciseJump:
http://www.vim.org/scripts/script.php?script_id=3437
2014-03-30 15:32 GMT+04:00 Yasuhiro MATSUMOTO mattn...@gmail.com:
index(sprit(こんにちわ世界, \zs), 世) should return 5
It does, but you have 2 typos: not sprit but split, and \zs should be in
single quotes, not double:
index(split(こんにちわ世界, '\zs'), 世)
But anyway all these solutions are so dirty
2014-03-30 17:00 GMT+04:00 Andre Sihera andre.sih...@hotmail.co.jp:
On 30/03/14 20:32, Yasuhiro MATSUMOTO wrote:
index(sprit(こんにちわ世界, \zs), 世) should return 5
Now this is interesting.
index() does indeed split on character, not byteboundaries. However, even
if
I can do this:
2014-03-30 20:04 GMT+04:00 Yasuhiro MATSUMOTO mattn...@gmail.com:
This is not good. These inconsistencies need to be fixed.
No, don't break compatibility.
vim script should handle bytes as index.
We already have mentioned, and not once, that nobody wants to break
compatibility, but we want
Hello all.
match() function returns index of first match, but if there are multi-byte
chars before first match, then each multi-byte chars is interpreted as
several chars, so, index becomes wrong.
Say, match(foobar, bar) returns 3, which is correct. But
match(яfoobar, bar) returns 5, which is
2014-03-30 3:34 GMT+04:00 Dmitry Frank dimon.fr...@gmail.com:
Hello all.
match() function returns index of first match, but if there are multi-byte
chars before first match, then each multi-byte chars is interpreted as
several chars, so, index becomes wrong.
Say, match(foobar, bar) returns
@gmail.com:
On Mar 30, 2014 3:35 AM, Dmitry Frank dimon.fr...@gmail.com wrote:
Hello all.
match() function returns index of first match, but if there are
multi-byte chars before first match, then each multi-byte chars is
interpreted as several chars, so, index becomes wrong.
Say
So, is this issue fixed now? If yes, then which patch should fix it?
2013/9/5 Bram Moolenaar b...@moolenaar.net
Christian Brabandt wrote:
On Di, 03 Sep 2013, Ken Takata wrote:
2013/09/04 Wed 11:04:38 UTC+9 Shougo wrote:
I think this problem is caused by Vim 7.3.1269.
Thank you very much!
2013/9/11 Christian Brabandt cbli...@256bit.org
On Wed, September 11, 2013 14:07, Dmitry Frank wrote:
So, is this issue fixed now? If yes, then which patch should fix it?
7.4.018
regards,
Christian
--
--
You received this message from the vim_dev maillist.
Do
Hello.
I used very old Vim 7.3.46 before (on Windows), now I tried Vim 7.4, and I
have an issue with popup-menu.
Say, I have popup-menu with three items: one, two, three.
In Vim 7.3, when I type part of word, first menuitem keeps being selected,
so, I can just type o, press Enter, and one is
Thanks again!
2012/9/28 Christian Brabandt cbli...@256bit.org
On Fri, September 28, 2012 08:01, Dmitry Frank wrote:
Thank you very much for your attention, but will this patch be applied in
official release?
It is patch 7.3.646
regards,
Christian
--
You received this message from
Thank you very much for your attention, but will this patch be applied in
official release?
2012/8/27 Christian Brabandt cbli...@256bit.org
Hi Dmitry!
On Sa, 25 Aug 2012, Dmitry Frank wrote:
2012/8/25 Christian Brabandt cbli...@256bit.org
Hi Dmitry!
On Sa, 25 Aug 2012, Dmitry
Dear developers,
There is an issue with persistent undo history. Steps to reproduce:
*) Make sure you have set up persistent undo in Vim.
*) Open any file in vim, made some changes, save the file. (changes needed
to add changesets to the undo history)
*) Open the same file in any different app,
reloaded changes as just a
single change in undohistory*. This is really good, check this.
But if user close Vim now, then these changes is lost.
--
Regards,
Dmitry.
2012/8/25 James McCoy james...@jamessan.com
On Sat, Aug 25, 2012 at 04:03:54PM +0400, Dmitry Frank wrote:
*) Make sure you have
2012/8/25 Christian Brabandt cbli...@256bit.org
Hi Dmitry!
On Sa, 25 Aug 2012, Dmitry Frank wrote:
Of course, if you close Vim, then change file by another app, then open
this file in Vim again, then, expectedly, undo history should be lost.
But in my example, Vim reloads the changes
Hello.
I have a question about syn-conceal.
I have concealcursor=nc and this works fine except one thing: say, I have
a following line: foo bar ~*baz*~ foo, and symbols ~ and * are
concealed. I move cursor through this line, and cursor stuck on concealed
symbols.
And this isn't worse thing:
19 matches
Mail list logo
