I don't know if the problem is having two dictionaries or specifically with the
Hebrew dictionary, but if I have an English text and press Ctrl-N to complete a
word, I get an initial display of matches and then Vim freezes up with a
"searching..." message on the status line.
If I change "spella
Patch adds fail_if_missing test that was missing for Python 3.
diff -r c628346c7f96 src/configure.in
--- a/src/configure.in Thu Jun 13 22:59:30 2013 +0200
+++ b/src/configure.in Fri Jun 14 08:15:18 2013 +0200
@@ -1229,6 +1229,9 @@
AC_MSG_RESULT(too old)
fi
fi
+ if test "$fail_if
On Friday, June 14, 2013 4:15:03 AM UTC+2, Heptite wrote:
> On Thu, 13 Jun 2013, Andrei Olsen wrote:
>
>
>
> > On Friday, June 14, 2013 3:36:44 AM UTC+2, Zulox4 wrote:
>
> >> E518: Unknown option: set
>
> >>
>
> >> My .vimrc file have one line:
>
> >>
>
> >> set smartindent set tabstop=2 se
On Friday, June 14, 2013 11:52:23 AM UTC+8, ZyX wrote:
> On Jun 14, 2013 7:41 AM, "Bohr Shaw" wrote:
>
> >
>
> > I compile vim against two system python versions without any problem. But I
> > get the "E370:Could not load library libpython2.7.a" when I compile vim
> > against self compiled pyt
On Jun 14, 2013 7:41 AM, "Bohr Shaw" wrote:
>
> I compile vim against two system python versions without any problem. But
I get the "E370:Could not load library libpython2.7.a" when I compile vim
against self compiled python versions.
>
> I just change my environment path to point to the correct p
> > What you say hints that the JIT one is always better. So why not use
> > luajit when it's available, falling back to non-JIT when it's not?
> > Then it would work well for people who don't even know about the option.
> > Right?
> >
> > The option might still be useful to force using one or th
I compile vim against two system python versions without any problem. But I get
the "E370:Could not load library libpython2.7.a" when I compile vim against
self compiled python versions.
I just change my environment path to point to the correct python versions
before I compile vim. Although I c
after ruby code:
'asdf'<<"||"<<'asdfasdf'
syntax highlight has broken
--
--
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 be
On Thu, 13 Jun 2013, Andrei Olsen wrote:
On Friday, June 14, 2013 3:36:44 AM UTC+2, Zulox4 wrote:
E518: Unknown option: set
My .vimrc file have one line:
set smartindent set tabstop=2 set shiftwidth=2 set expandtab
Put your commands on separate lines, i.e.
set smartindent
set tabstop=2
etc.
On Friday, June 14, 2013 9:36:44 AM UTC+8, Zulox4 wrote:
> Hello,
>
> When Vim 7.3.1189 win32 console start it display this error (the next five
> lines) :
>
> C:\Vim_20130614_1189\vim\src>vim
> Error detected while processing C:\Users\vim7user_win7sp1\.vimrc:
> line1:
> E518: Unknown option
On Friday, June 14, 2013 3:36:44 AM UTC+2, Zulox4 wrote:
> Hello,
>
> When Vim 7.3.1189 win32 console start it display this error (the next five
> lines) :
>
> C:\Vim_20130614_1189\vim\src>vim
> Error detected while processing C:\Users\vim7user_win7sp1\.vimrc:
> line1:
> E518: Unknown option
If you want to write settinsg per one line.
set smartindent set tabstop=2 set shiftwidth=2 set expandtab
This should be:
set smartindent tabstop=2 shiftwidth=2 expandtab
On Friday, June 14, 2013 10:36:44 AM UTC+9, Zulox4 wrote:
> Hello,
>
> When Vim 7.3.1189 win32 console start it display this
Hello,
When Vim 7.3.1189 win32 console start it display this error (the next five
lines) :
C:\Vim_20130614_1189\vim\src>vim
Error detected while processing C:\Users\vim7user_win7sp1\.vimrc:
line1:
E518: Unknown option: set
Press ENTER or type command to continue
My .vimrc file have one lin
I'm working on a project to make vim produce speech output.
https://code.google.com/p/phonim/
As part of the solution, we want to use autocommands such as CursorMoved
and CursorMovedI to trigger speech. Is there an equivalent event for Visual
mode?
Thanks,
Mike Panciera
--
--
You received th
On Friday, June 14, 2013 1:14:59 AM UTC+8, ZyX wrote:
> On Thursday, June 13, 2013 7:22:20 PM UTC+4, Bohr Shaw wrote:
>
> > I have added the exact python library DLL to the shell's search
> > path($PATH). But I still get the error: "E370, Could not load the library
> > libpython*."
>
> >
>
>
On Thu, Jun 13, 2013 at 10:35 PM, Bram Moolenaar wrote:
>
> Hiroshi Shirosaki wrote:
>
>> Recently some vim plugins use if_lua for performance issues because
>> Vim script is not so fast. For example Shougo's neocomplete.vim[1]
>> shows better performance thanks to if_lua.
>>
>> According to some
Patch 7.3.1189 (after 7.3.1185)
Problem:Highlighting is still wrong sometimes. (Dominique Pelle)
Solution: Also restore reginput properly.
Files: src/regexp_nfa.c
*** ../vim-7.3.1188/src/regexp_nfa.c2013-06-13 20:19:35.0 +0200
--- src/regexp_nfa.c2013-06-13 22:52:38.00
Patch 7.3.1188
Problem:Newline characters messing up error message.
Solution: Remove the newlines. (Kazunobu Kuriyama)
Files: src/gui_x11.c
*** ../vim-7.3.1187/src/gui_x11.c 2010-11-16 15:04:51.0 +0100
--- src/gui_x11.c 2013-06-13 21:54:39.0 +0200
*
Kazunobu Kuriyama wrote:
> While configuring guifontset to have gvim work on my MacBook, I got
> the error message shown below (the content of the message itself is
> irrelevant to the bug I want to point out here, so you don't need to
> figure out what it says):
>
> E253: Fontset name:
> -bitst
Patch 7.3.1187 (after 7.3.1170)
Problem:"s:" is recognized but "" is not. (ZyX)
Solution: Translate "" like "s:".
Files: src/eval.c
*** ../vim-7.3.1186/src/eval.c 2013-06-12 22:08:54.0 +0200
--- src/eval.c 2013-06-13 21:15:58.0 +0200
***
*** 10976,10996 *
Patch 7.3.1186
Problem:Python 3: test 87 may crash.
Solution: Use _PyArg_Parse_SizeT instead of PyArg_Parse. (Jun Takimoto)
Files: src/if_python3.c
*** ../vim-7.3.1185/src/if_python3.c2013-06-12 14:40:58.0 +0200
--- src/if_python3.c2013-06-13 20:44:48.0 +0200
*
Steven Oliver wrote:
> I spoke with the maintainer of the ABAP syntax code and got the latest
> version from him. Would you mind including it in your next round runtime
> file updates?
That's a tiny change. I'll include it. And update the date in the
header.
--
hundred-and-one symptoms of be
Jun Takimoto wrote:
> On 2013/06/12, at 21:41, Bram Moolenaar wrote:
> > Thanks for the updates. Unfortunately, now both test 86 and 87 fail for
> > me.
> (snip)
> > -2,xx
> > -before
> > -after
>
> I'm getting the same error (python2.7.3 and python 3.2.3).
>
> It seems the tests are failing
SungHyun Nam wrote:
> $ cat test
>
> a
> b
> c
>
> $ vim -u NONE --noplugin test
> /a\n\(^b$\n\)\{1,2}c
>
> The search failed with re=0. If I set 're=1', search works.
Thanks for reporting. It's easy to reproduce.
Strange that this wasn't caught before.
Looks like the actual problem is mat
Patch 7.3.1185
Problem:New regexp engine: no match with ^ after \n. (SungHyun Nam)
Solution: Fix it, add a test.
Files: src/regexp_nfa.c, src/testdir/test64.in, src/testdir/test64.ok
*** ../vim-7.3.1184/src/regexp_nfa.c2013-06-13 19:47:03.0 +0200
--- src/regexp_nfa.c20
Bram,
I spoke with the maintainer of the ABAP syntax code and got the latest
version from him. Would you mind including it in your next round runtime
file updates?
Steven N. Oliver
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you a
On Thu, Jun 13, 2013 at 1:46 PM, Bram Moolenaar wrote:
>
> Manuel Ortega wrote:
>
> > Something's up with hg. I did 'hg pull -u' to get this commit, but those
> > empty files are not actually put into the working dir. 'hg sum' tells me
> > that indeed I did receive 7.3.1183.
> >
> > Then I manu
Patch 7.3.1184
Problem:Highlighting is sometimes wrong. (Axel Bender)
Solution: Fetch regline again when returning from recursive regmatch.
Files: src/regexp_nfa.c
*** ../vim-7.3.1183/src/regexp_nfa.c2013-06-11 22:44:03.0 +0200
--- src/regexp_nfa.c2013-06-13 19:32:31.0
Manuel Ortega wrote:
> On Thu, Jun 13, 2013 at 1:27 PM, Bram Moolenaar wrote:
>
> >
> > Patch 7.3.1183
> > Problem:Python tests 86 and 87 fail.
> > Solution: Add "empty" files. (ZyX)
> > Files: src/testdir/python_before/before_1.py,
> > src/testdir/python_before/before_2.
On Thu, Jun 13, 2013 at 1:27 PM, Bram Moolenaar wrote:
>
> Patch 7.3.1183
> Problem:Python tests 86 and 87 fail.
> Solution: Add "empty" files. (ZyX)
> Files: src/testdir/python_before/before_1.py,
> src/testdir/python_before/before_2.py
>
>
> *** ../vim-7.3.1182/src/testdi
ZyX wrote:
> > > Thanks for the updates. Unfortunately, now both test 86 and 87
> > > fail for me. Previously only test 86 was failing.
> Some files are missing in the diff, but [present](
> https://bitbucket.org/ZyX_I/vim/commits/a1b8a5ddecec70085e7e62f8ea9bc6c46ecea530#chg-src/testdir/python
Patch 7.3.1183
Problem:Python tests 86 and 87 fail.
Solution: Add "empty" files. (ZyX)
Files: src/testdir/python_before/before_1.py,
src/testdir/python_before/before_2.py
*** ../vim-7.3.1182/src/testdir/python_before/before_1.py 2013-06-13
19:26:45.0 +0200
-
On Thursday, June 13, 2013 7:22:20 PM UTC+4, Bohr Shaw wrote:
> I have added the exact python library DLL to the shell's search path($PATH).
> But I still get the error: "E370, Could not load the library libpython*."
>
> I have check the related document which says: In a console window type "pat
Ken, sorry for the false report. The problem disappeared with a fresh build
after the equivalent of a make clean.
Ben, yes, I had meant a directory junction created with mklink /J
Ajit
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
I have added the exact python library DLL to the shell's search path($PATH).
But I still get the error: "E370, Could not load the library libpython*."
I have check the related document which says: In a console window type "path"
to see what directories are used. What does this mean?
--
--
Yo
Hi,
While configuring guifontset to have gvim work on my MacBook, I got the error
message shown below (the content of the message itself is irrelevant to the bug
I want to point out here, so you don't need to figure out what it says):
E253: Fontset name:
-bitstream-menlo-medium-r-normal--12-*-
On Thursday, June 13, 2013 10:15:11 AM UTC-5, Ken Takata wrote:
> Hi Ajit,
>
> 2013/06/13 Thu 22:59:42 UTC+9 Ajit Thakkar wrote:
> > 32-bit gVim 7.3.1182 (features=normal) on 64-bit Win7+SP1 freezes when I
> > attempt to edit any file in a directory that is hard linked to another
> > directory.
Hi Ajit,
2013/06/13 Thu 22:59:42 UTC+9 Ajit Thakkar wrote:
> 32-bit gVim 7.3.1182 (features=normal) on 64-bit Win7+SP1 freezes when I
> attempt to edit any file in a directory that is hard linked to another
> directory. After killing the process, a second attempt to edit the same file
> reveals
- Original Message -
> From: "Bram Moolenaar"
>
> Rob Owens wrote:
>
> > I made a dumb newbie error on my diff files, so I'm sending the
> > updated ones. This time I used the vim files from mercurial
> > instead
> > of Debian's versions (headsmack!)
> >
> > Syntax files are attached.
32-bit gVim 7.3.1182 (features=normal) on 64-bit Win7+SP1 freezes when I
attempt to edit any file in a directory that is hard linked to another
directory. After killing the process, a second attempt to edit the same file
reveals that a swap file was created. backupcopy is not changed from its
d
Hiroshi Shirosaki wrote:
> Recently some vim plugins use if_lua for performance issues because
> Vim script is not so fast. For example Shougo's neocomplete.vim[1]
> shows better performance thanks to if_lua.
>
> According to some benchmark results LuaJIT looks much faster than Lua
> and is full
* Jun T. [2013-06-13 13:42 +0900]:
[...]
> In addition, if I configure --with-python3interp=dynamic,
> test87 core dumps.
> This core dump can be fixed by the following patch:
>
>
> diff -r 8a49630c8a5f src/if_python3.c
> --- a/src/if_python3.cWed Jun 12 22:41:37 2013 +0200
> +++ b/src/
Hi,
Recently some vim plugins use if_lua for performance issues because Vim script
is not so fast. For example Shougo's neocomplete.vim[1] shows better
performance thanks to if_lua.
According to some benchmark results LuaJIT looks much faster than Lua and is
fully compatible to Lua 5.1.[2][3]
On Jun 13, 2013 2:40 PM, "Bram Moolenaar" wrote:
>
>
> ZyX wrote:
>
> > > > # HG changeset patch
> > > > # User ZyX
> > > > # Date 1371036594 -14400
> > > > # Wed Jun 12 15:29:54 2013 +0400
> > > > # Branch python-path
> > > > # Node ID 27aa091d5fa525fd4ba97b4b68dc62e64e8bd3a0
> > > > # Pare
Dominique Pellé wrote:
> > Bram Moolenaar wrote:
> >
> >> Axel Bender wrote:
> >>
> >>> you may as well elimitate the inverted question mark (I just forgot to
> >>> replace it in the example - in the base document there are no xs), the
> >>> result is the same.
> >>> Also, the effect is indepen
On Thursday, June 13, 2013 6:31:42 PM UTC+12, SungHyun Nam wrote:
> /a\n\(^b$\n\)\{1,2}c
I see this, too; it can be simplified to
/a\n^b$
for me to see a difference. The ^ does not match with re=0, though the help
says it should after a \n.
Regards, John Little
--
--
You received this mes
ZyX wrote:
> > > # HG changeset patch
> > > # User ZyX
> > > # Date 1371036594 -14400
> > > # Wed Jun 12 15:29:54 2013 +0400
> > > # Branch python-path
> > > # Node ID 27aa091d5fa525fd4ba97b4b68dc62e64e8bd3a0
> > > # Parent 643f64bbd9386d746313a7678cfa08826b4a5122
> > > Use the same method
47 matches
Mail list logo
