On Thursday, June 21, 2012 10:30:55 PM UTC+2, Nicolas Holzschuch wrote:
Hello,
I am trying to extend the Applidium port of vim to iOS.
Specifically, I'm trying to add support of external keyboards (the iPad is
great, but it's even more useful with an external keyboard.
On 2013-06-05 Wednesday at 12:43 +0200 Bram Moolenaar wrote:
Roland Eggner wrote:
After update 7.3.{865,969} I notice this regression:
“:wviminfo! filename” writes only new history entries, misses old
entries read by “:rviminfo! filename”. “:history” shows old and new
entries properly,
Shougo wrote:
Hi, I found the split() result problem.
If regexpengine is 0:
:echo split(foo\XFFbar, '[\xFF]')
= ['fooffbar']
:echo split(foo\XFFbar, \xFF)
= ['fooffbar']
If regexpengine is 1:
:echo split(foo\XFFbar, '[\xFF]')
= ['foo', 'bar']
:echo split(foo\XFFbar, \xFF)
Dominique Pelle wrote:
eBram Moolenaar wrote:
You can enable the profiler in the Makefile. The one using Gmon only
measures time per function though. I already know that addstate() is
taking most time. Need to try to reduce the number of calls.
Opening this xml file...
Hi, list.
When map nul to something like follow:
map nul nul
And do :map nul for display the map, it shows strange X instead of Nul:
X nul
Below is a patch
https://gist.github.com/mattn/5720601
Please check and include.
I received this patch from DeaR on github.
Thanks.
--
--
You
Hi list.
When type :function Foo for existing function Foo, it should be shown the
function code with function attributes abort/dict/range.
:function! Foo() abort
: echo foo
:endfunction
:function Foo
function Foo() abort
1echo foo
endfunction
Below is a patch.
On 06/06/2013 10:38, Bram Moolenaar wrote:
Dominique Pelle wrote:
eBram Moolenaar wrote:
You can enable the profiler in the Makefile. The one using Gmon only
measures time per function though. I already know that addstate() is
taking most time. Need to try to reduce the number of calls.
Hello
I have updated Russian menu translation (in attachment). I try to contact
with Vassily Ragosin (previous translator in year 2004) via e-mail, but I
can't.
Thanks!
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Patch 7.3.1129
Problem:Can't see what pattern in syntax highlighting is slow.
Solution: Add the :syntime command.
Files: src/structs.h, src/syntax.c, src/ex_cmds.h, src/ex_docmd.c,
src/proto/syntax.pro, src/ex_cmds2.c, src/proto/ex_cmds2.pro,
Mike Williams wrote:
[...]
Clearly the new engine is much faster for long lines (5000 chars). The
old engine comes to a grinding halt there.
I'm planning to add profiling to syntax patterns, so that we can see
which pattern is taking most time. This will help both optimizing the
On Thursday, June 6, 2013 9:02:22 PM UTC+9, Bram Moolenaar wrote:
Patch 7.3.1129
Problem:Can't see what pattern in syntax highlighting is slow.
Solution: Add the :syntime command.
Files:src/structs.h, src/syntax.c, src/ex_cmds.h, src/ex_docmd.c,
When compiling 7.3.1129 (Windows 7 64 bit, MinGW), I get the following error
message (7.3.1128 compiled with no errors):
gcc -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF
-DFEAT_BIG -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT
-DFEAT_OLE -DFEAT_CSCOPE
Patch 7.3.1130 (after 7.3.1129)
Problem:Can't build with anything but huge features.
Solution: Check for FEAT_PROFILE. (Yasuhiro Matsumoto)
Files: src/ex_docmd.c, src/structs.h, src/syntax.c
*** ../vim-7.3.1129/src/ex_docmd.c 2013-06-06 14:01:35.0 +0200
---
Yasuhiro Matsumoto wrote:
On Thursday, June 6, 2013 9:02:22 PM UTC+9, Bram Moolenaar wrote:
Patch 7.3.1129
Problem:Can't see what pattern in syntax highlighting is slow.
Solution: Add the :syntime command.
Files: src/structs.h, src/syntax.c, src/ex_cmds.h,
Same with 1130...
--
--
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 subscribed to the Google Groups
vim_dev
Ok after new pull with 1130.
--
--
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 subscribed to the Google
What error?
On 6/6/13, Axel Bender axel.ben...@cip-kommunal.de wrote:
Same with 1130...
--
--
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
Patch 7.3.1131
Problem:New regexp engine is a bit slow.
Solution: Do not clear the state list. Don't copy syntax submatches when
not used.
Files: src/regexp_nfa.c
*** ../vim-7.3.1130/src/regexp_nfa.c2013-06-05 21:42:49.0 +0200
--- src/regexp_nfa.c
On Wednesday, June 5, 2013 9:04:38 PM UTC-5, hiwa wrote:
I have made and gotten 7.3.1119 from Mercurial on Ubuntu 10.10.
Simple program exit via :q and :wq etc. freezes entire gvim.
Edited result is not saved after a forced process killing.
What could be the cause and the solution
On Thursday, June 6, 2013 3:08:24 AM UTC-5, Roland Eggner wrote:
On 2013-06-05 Wednesday at 12:43 +0200 Bram Moolenaar wrote:
Roland Eggner wrote:
After update 7.3.{865,969} I notice this regression:
“:wviminfo! filename” writes only new history entries, misses old
entries read
Patch 7.3.1132
Problem:Crash when debugging regexp.
Solution: Do not try to dump subexpr that were not set. Skip over count of
\% items.
Files: src/regexp.c, src/regexp_nfa.c
*** ../vim-7.3.1131/src/regexp.c2013-06-05 21:42:49.0 +0200
--- src/regexp.c
Patch 7.3.1133
Problem:New regexp engine is a bit slow.
Solution: Skip ahead to a character that must match. Don't try matching a
^ patter past the start of line.
Files: src/regexp_nfa.c, src/regexp.h
*** ../vim-7.3.1132/src/regexp_nfa.c2013-06-06 18:04:47.0
Patch 7.3.1134
Problem:Running test 49 takes a long time.
Solution: Don't have it grep all files.
Files: src/testdir/test49.vim
*** ../vim-7.3.1133/src/testdir/test49.vim 2013-02-26 22:54:06.0
+0100
--- src/testdir/test49.vim 2013-06-06 18:13:46.0 +0200
On Wednesday, June 5, 2013 5:43:40 PM UTC-5, Andrei Olsen wrote:
On Thursday, June 6, 2013 12:32:41 AM UTC+2, Ben Fritz wrote:
On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
gcc: unrecognized option
Steven Oliver wrote:
Please accept the following zip file that contains three updated runtime
files for the Falcon programming language.
The indent file was completely rewritten based upon the ruby version.
The syntax file now includes some (optional, but neat) rainbow
highlighting.
And,
Ben Fritz wrote:
On Wednesday, June 5, 2013 5:43:40 PM UTC-5, Andrei Olsen wrote:
On Thursday, June 6, 2013 12:32:41 AM UTC+2, Ben Fritz wrote:
On Wednesday, June 5, 2013 5:27:27 PM UTC-5, Andrei Olsen wrote:
On Wednesday, June 5, 2013 11:47:43 PM UTC+2, Ben Fritz wrote:
gcc:
Patch 7.3.1135
Problem:Compiler warning for unused argument.
Solution: Add UNUSED.
Files: src/syntax.c
*** ../vim-7.3.1134/src/syntax.c2013-06-06 14:55:16.0 +0200
--- src/syntax.c2013-06-06 21:18:20.0 +0200
***
*** 3258,3264
Sergey Alyoshin wrote:
I have updated Russian menu translation (in attachment). I try to contact
with Vassily Ragosin (previous translator in year 2004) via e-mail, but I
can't.
Thanks. I haven't heard from Vassily for years.
I'll change the header to mention the previous maintainer.
Patch 7.3.1136
Problem::func Foo does not show attributes.
Solution: Add abort, dict and range. (Yasuhiro Matsumoto)
Files: src/eval.c
*** ../vim-7.3.1135/src/eval.c 2013-05-30 13:37:23.0 +0200
--- src/eval.c 2013-06-06 21:29:06.0 +0200
***
***
Yasuhiro Matsumoto wrote:
When type :function Foo for existing function Foo, it should be shown
the function code with function attributes abort/dict/range.
:function! Foo() abort
: echo foo
:endfunction
:function Foo
function Foo() abort
1echo foo
endfunction
Below is
I wrote:
Steven Oliver wrote:
Please accept the following zip file that contains three updated runtime
files for the Falcon programming language.
The indent file was completely rewritten based upon the ruby version.
The syntax file now includes some (optional, but neat) rainbow
Hi Ben!
On 2013-06-06 Thursday at 07:27 -0700 Ben Fritz wrote:
On Thursday, June 6, 2013 3:08:24 AM UTC-5, Roland Eggner wrote:
… …
I reported not clearly enough, I am afraid. There are 2 probably related
bugs:
(1) Commit “7.3.880 Problem: When writing viminfo, old history lines
On Thu, Jun 6, 2013 at 2:37 PM, Roland Eggner ed...@systemanalysen.net wrote:
Hi Ben!
On 2013-06-06 Thursday at 07:27 -0700 Ben Fritz wrote:
On Thursday, June 6, 2013 3:08:24 AM UTC-5, Roland Eggner wrote:
… …
I reported not clearly enough, I am afraid. There are 2 probably related
Hi
Attached patch fixes a memory leak in the
new command :syntime report introduced
in patch 7.3.1129.
:syntime is a great new feature. Thanks!
Dominique
--
--
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
* Bram Moolenaar b...@moolenaar.net [2013-05-31 20:49 +0200]:
[...]
Note that this solves it by commenting out a function that apparently
fails. I hope you can figure out why it fails, so we can re-enable the
tests.
[...]
* Jun T. takimot...@kba.biglobe.ne.jp [2013-06-06 10:39 +0900]:
Hi
Hi Charles,
2013/06/01 Sat 15:25:15 UTC+9 Dominique Pelle wrote:
Ken Takata ken...@csc.jp wrote:
Hi Charles,
After updating Vim to 7.3.919 or later, I can't open *.ja including
README.ja (a README file written in Japanese).
When I try to open *.ja, I get the following message:
On 2013-06-06, Ken Takata wrote:
Hi Charles,
2013/06/01 Sat 15:25:15 UTC+9 Dominique Pelle wrote:
Ken Takata ken...@csc.jp wrote:
Hi Charles,
After updating Vim to 7.3.919 or later, I can't open *.ja including
README.ja (a README file written in Japanese).
When I try to
I wrote:
Steven Oliver wrote:
Please accept the following zip file that contains three updated runtime
files for the Falcon programming language.
The indent file was completely rewritten based upon the ruby version.
The syntax file now includes some (optional, but neat)
No.
In japanese, many users uses *.ja file extention. And they may start
to write the text with leading letter 'PK'. For example, abbreviation
of 'Penalty Kick'.
Please don't use workarround.
On 6/7/13, Gary Johnson garyj...@spocom.com wrote:
On 2013-06-06, Ken Takata wrote:
Hi Charles,
Hi Bram,
This is just a reminder about updating the manifest before you release
7.4. See below ...
---
src/gvim.exe.mnf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gvim.exe.mnf b/src/gvim.exe.mnf
index 26ade97f033e..206fd2b12ec8 100644
--- a/src/gvim.exe.mnf
+++
I think this is much easier to use than the old way comparing v:version
and has('patchN')
Marc Weber
--
--
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
---
Hi,
Moving cursor of filetype=eruby is also much slower with Vim 7.3.1136
regexpengine=0.
Here is a result of syntime.
https://gist.github.com/shirosaki/5726164
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
2013年6月6日木曜日 18時38分58秒 UTC+9 Bram Moolenaar:
Shougo wrote:
Hi, I found the split() result problem.
If regexpengine is 0:
:echo split(foo\XFFbar, '[\xFF]')
= ['fooffbar']
:echo split(foo\XFFbar, \xFF)
= ['fooffbar']
If regexpengine is 1:
On Friday, June 7, 2013 8:38:02 AM UTC+9, Gary Johnson wrote:
On 2013-06-07, Yasuhiro MATSUMOTO wrote:
No.
In japanese, many users uses *.ja file extention. And they may start
to write the text with leading letter 'PK'. For example, abbreviation
of 'Penalty Kick'.
Please
44 matches
Mail list logo
