Could you add paredit : http://www.vim.org/scripts/script.php?script_id=3998
to the vim plugin runtime files ?
I'd rather vote for adding an official package manager and leave it to the
users to decide whether they want to add this plugin.
--
--
You received this message from the vim_dev
Marcin said:
I am not sure why it get's three Z though. I'd expected to see only two of
them.
The last z eats the first Z, if there are an odd number of z's, as z is a
prefix to two key commands.
Regards, John Little
--
--
You received this message from the vim_dev maillist.
Do not
I confirm that :
$ sudo make install STRIP=/usr/bin/true
Work's fine.
Why I've never see this command on other topics with all the people complaining
that vim doesn't work well with ruby + os X ?
I will try this night on an older macbook running OS X 10.6.7
Thanks for the reply.
Le lundi 8
You said it's because of ruby 2.0,
But I tried to compile with ruby 1.8.7 (on the system)
and 1.9.3, and it ends with the same problem.
Thanks for the solution.
Le lundi 8 juillet 2013 18:20:36 UTC+2, Kent Sibilev a écrit :
On Monday, July 8, 2013 7:25:03 AM UTC-4, Timothee Gauthier wrote:
Hi list,
I noticed that using Vim 7.4a the Vimwiki plugin works measurably slower with
re=0 than with re=1. I figured out the reason is this regexp in the syntax
definition:
Ben Fritz wrote:
On Mon, Jul 8, 2013 at 1:59 PM, Bram Moolenaar b...@moolenaar.net wrote:
Benjamin Fritz wrote:
On Thu, Jul 4, 2013 at 4:44 AM, Bram Moolenaar b...@moolenaar.net wrote:
Does the delimitMate return the text to be inserted or does it use
setline()? In the last case
Patch 7.4a.003
Problem:Copyright year is oudated.
Solution: Only use the first year.
Files: src/vim.rc, src/vim16.rc
*** ../vim-7.4a.002/src/vim.rc 2013-06-16 16:37:33.0 +0200
--- src/vim.rc 2013-07-08 20:38:16.0 +0200
***
*** 91,97
VALUE
On 08/07/13 20:59, Bram Moolenaar wrote:
Ken Takata wrote:
Copyright year in vim.rc (and vim16.rc) seems old.
I think it's better to move to version.h.
Please check the attached patch.
Actually, I have been told that only the first year matters.
So we can just keep 1996.
Note that under
Raymond Ko wrote:
The following mini-patch adds support for Microsoft Visual Studio 2012
Update 3, which has bumped their version number in the compiler.
I have tested this and can confirm that a vim executable is
successfully produced.
Thanks, I'll include it.
--
Lawmakers made it
Patch 7.4a.004
Problem:MSVC 2012 Update 3 is not recognized.
Solution: Add the version number. (Raymond Ko)
Files: src/Make_mvc.mak
*** ../vim-7.4a.003/src/Make_mvc.mak2013-06-03 20:09:58.0 +0200
--- src/Make_mvc.mak2013-07-09 13:13:12.0 +0200
***
Tony Mechelynck wrote:
On 08/07/13 20:59, Bram Moolenaar wrote:
Ken Takata wrote:
Copyright year in vim.rc (and vim16.rc) seems old.
I think it's better to move to version.h.
Please check the attached patch.
Actually, I have been told that only the first year matters.
So we
Lech Lorens wrote:
On 30-Jun-2013 Lech Lorens lech.lor...@gmail.com wrote:
On 30-Jun-2013 Bram Moolenaar b...@moolenaar.net wrote:
The fix seems OK. But the test already passes without it.
Yes, this is what I tried to explain above but somehow didn't make it
clear ;-)
Also,
Patch 7.4a.005
Problem:Scroll binding causes unexpected scroll.
Solution: Store the topline after updating scroll binding. Add a test.
(Lech Lorens)
Files: src/testdir/test98.in, src/testdir/test98a.in,
src/testdir/test98.ok, src/option.c,
Patch 7.4a.006
Problem:Failure in po file check goes unnoticed.
Solution: Fail make test if the po file check fails.
Files: src/Makefile
*** ../vim-7.4a.005/src/Makefile2013-07-06 14:33:40.0 +0200
--- src/Makefile2013-07-09 14:54:43.0 +0200
Sergey Alyoshin wrote:
Updated Russian translation for Vim 7.4
Thanks!
--
Living on Earth includes an annual free trip around the Sun.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
Hi list,
1. vim -nNX -u NONE
2. :se ve=all
3. 3otestesc
4. g$
Then I expect k to move me up in the same column but it goes at $ in the
previous line.
Note: in step 4 if I move to g$ using l then k moves the cursor
correctly
Cheers
PS:
VIM - Vi IMproved 7.4a BETA (2013 Jul 6,
Raf wrote:
Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is the first BETA release of Vim 7.4.
Please check that the distribution is OK. I haven't done one for a long
time. Report anything that isn't right. That includes a crash but also
a typo
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
After this patch, build was failed like this
Mismatching error/warning code in line 3006
make[2]: *** [nl.ck] Error 1
make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po'
make[1]: *** [test] Error 2
Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799
I believe I saw this fixed earlier, or something related.
I have tested this with:
:ver
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 9 2013 09:34:36)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-6
Compiled by me
Big version with GUI. Features included (+) or not
On Tue, July 9, 2013 15:15, Dimitar DIMITROV wrote:
Hi list,
1. vim -nNX -u NONE
2. :se ve=all
3. 3otestesc
4. g$
Then I expect k to move me up in the same column but it goes at $ in the
previous line.
Note: in step 4 if I move to g$ using l then k moves the cursor
correctly
Dimitar Dimitrov wrote:
Hi list,
1. vim -nNX -u NONE
2. :se ve=all
3. 3otestesc
4. g$
Then I expect k to move me up in the same column but it goes at $ in
the previous line.
Note: in step 4 if I move to g$ using l then k moves the
cursor correctly
Cheers
PS:
VIM -
Hi,
One more patch attached :-)
Regards,
Ken Takata
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are
File: runtime/indent/python.vim
When checking for a colon at the end of a statement to decide whether to indent
the next line, it strips trailing comments; however, the syntax group can be
pythonTodo rather than pythonComment, which it was not detecting.
Thus, a line like this:
if True:
On Tue, Jul 9, 2013 at 5:54 AM, Bram Moolenaar b...@moolenaar.net wrote:
That can be done by returning cursor key sequences. No need for
setline():
imap ( C-R=LeftParen()CR
fun! LeftParen()
return ()\Left
endfun
imap ) C-R=RightParen()CR
On Tue, Jul 9, 2013 at 1:06 AM, glts 676c7...@gmail.com wrote:
On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is the first BETA release of Vim 7.4.
Please check that the distribution is OK. I haven't done one
Hi,
:py3 vim.eval() doesn't handle multibyte characters properly
when 'encoding' is not utf-8 (e.g. cp932).
How to reproduce:
:set enc=cp932
:call setline(1, \u82a0) Set Hiragana Letter A 'あ' (U+3042 in Unicode)
:py3 import vim
:py3 print(vim.eval('getline(1)')) Printing 'あ' is expected.
Hi,
I saw the following thread in vim_use, and I found some mistakes in
function prototypes.
https://groups.google.com/d/topic/vim_use/_layXHD5hUk/discussion
Warning W8065 .\version.c 3504: Call to function 'list_features' with no
prototype in function list_version
Warning W8065 if_py_both.h
Ken Takata wrote:
One more patch attached :-)
Thanks.
--
ERIC IDLE PLAYED: THE DEAD COLLECTOR, MR BINT (A VILLAGE NE'ER-DO -WELL VERY
KEEN ON BURNING WITCHES), SIR ROBIN, THE GUARD WHO DOESN'T
HICOUGH BUT TRIES TO GET THINGS STRAIGHT, CONCORDE (SIR
David Fishburn wrote:
I believe I saw this fixed earlier, or something related.
I have tested this with:
:ver
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 9 2013 09:34:36)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-6
Compiled by me
Big version with
Thank you for describing. Now I understand what had happended.
2013/7/10 Bram Moolenaar b...@moolenaar.net:
Taro Muraoka wrote:
After this patch, build was failed like this
Mismatching error/warning code in line 3006
make[2]: *** [nl.ck] Error 1
make[2]: Leaving directory
On Tuesday, July 9, 2013 10:13:22 AM UTC-5, Bram Moolenaar wrote:
Ben Fritz wrote:
I don't remember how setline() solves the problem, but just returning
cursor sequences doesn't work, because it breaks undo/redo/repeat.
Yeah, that's true. I suppose we could avoid saving for undo
How about sending e-mail contains compile error to vim-dev from travis-ci?
On 7/10/13, Bram Moolenaar b...@moolenaar.net wrote:
Taro Muraoka wrote:
After this patch, build was failed like this
Mismatching error/warning code in line 3006
make[2]: *** [nl.ck] Error 1
make[2]: Leaving
Patch 7.4a.007
Problem:After g$ with 'virtualedit' set, k moves to a different
column. (Dimitar Dimitrov)
Solution: Set w_curswant. (Christian Brabandt)
Files: src/normal.c
*** ../vim-7.4a.006/src/normal.c2013-05-20 21:11:55.0 +0200
--- src/normal.c
Taro Muraoka wrote:
After this patch, build was failed like this
Mismatching error/warning code in line 3006
make[2]: *** [nl.ck] Error 1
make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po'
make[1]: *** [test] Error 2
Check this for details:
Patch 7.4a.008
Problem:Python 3 doesn't handle multibyte characters prooperly when
'encoding' is not utf-8.
Solution: Use PyUnicode_Decode() instead of PyUnicode_FromString(). (Ken
Takata)
Files: src/if_python3.c
*** ../vim-7.4a.007/src/if_python3.c
Ken Takata wrote:
:py3 vim.eval() doesn't handle multibyte characters properly
when 'encoding' is not utf-8 (e.g. cp932).
How to reproduce:
:set enc=cp932
:call setline(1, \u82a0) Set Hiragana Letter A 'あ' (U+3042 in Unicode)
:py3 import vim
:py3 print(vim.eval('getline(1)'))
Ben Fritz wrote:
On Tue, Jul 9, 2013 at 5:54 AM, Bram Moolenaar b...@moolenaar.net wrote:
That can be done by returning cursor key sequences. No need for
setline():
imap ( C-R=LeftParen()CR
fun! LeftParen()
return ()\Left
endfun
imap
Patch 7.4a.009
Problem:Compiler warnings for function prototypes.
Solution: Add void. Move list_features() prototype. (Ken Takata)
Files: src/gui_w48.c, src/if_py_both.h, src/version.c
*** ../vim-7.4a.008/src/gui_w48.c 2013-06-17 22:22:49.0 +0200
--- src/gui_w48.c
Chris Morgan wrote:
File: runtime/indent/python.vim
When checking for a colon at the end of a statement to decide whether
to indent the next line, it strips trailing comments; however, the
syntax group can be pythonTodo rather than pythonComment, which it was
not detecting.
Thus, a
Yasuhiro Matsumoto wrote:
How about sending e-mail contains compile error to vim-dev from travis-ci?
I rather have a human look at the message first to avoid false alarms.
If it's a real problem it should be easy to forward to vim-dev.
Unless you can automatically generate a patch to fix the
On Tue, Jul 9, 2013 at 4:22 PM, Yukihiro Nakadaira
yukihiro.nakada...@gmail.com wrote:
On Tue, Jul 9, 2013 at 1:06 AM, glts 676c7...@gmail.com wrote:
On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is the first BETA
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
Patch 7.4a.010
Problem:Test 86 and 97 fail when building with Python or Python 3 and
using a static library.
Solution: Add configure check to add -fPIE compiler flag.
Files: src/configure.in, src/auto/configure
*** ../vim-7.4a.009/src/configure.in2013-07-03
Dominique pelle wrote:
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp
Hi,
I've attached a patch to fix an issue where the wrong python3 config
directory is used when a system's sys.abiflags are empty.
Thanks,
Tim
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information,
I get E315 errors in Vim 7.4a, but not in Vim 7.3.829 and earlier.
In a nutshell, when a buffer in another window is modified via Python
buffer object, folds in the current buffer get messed up, jumping to
the last line results in multiple E315.
The script below shows how to reproduce (also
Bram Moolenaar wrote:
Raf wrote:
Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is the first BETA release of Vim 7.4.
Please check that the distribution is OK. I haven't done one for a long
time. Report anything that isn't right. That
It's wired. Did we make any big change between these revisions?
My system: Windows 7 with sp1. Before my upgrade, my Vim installed to
D:\Apps\Vim with following directory structure:
D:\Apps\Vim
vim73\ vim 7.3.1311
vimfiles\my plugins/colors, etc.
_vimrc
everything works
51 matches
Mail list logo
