What is the future of Vim?
It looks like glib/gtk .. people have done a lot of work on providing
automatic bindings to many important scripting languages.
Would it make sense to think about porting some important code (eg the
buffers) to such objects (which would still be plain old C only) - so
t
If we are at it - and other tools are already faster, is there a chance
to also add a engine 3 reusing the fast code?
If we partially break with VimL (by improving python support) why
not also add a commonly used regex syntax if speed is different.
I've tried debugging gnugrep which was said to
On 21/05/2013 05:04 a.m., Bram Moolenaar wrote:
>
> Cesar Romani wrote:
>
>> By updating from 7.3.969 to 7.3.981 the following command doesn't work
>> anymore:
>> %s/""/\='"'.matchstr(getline("."), '\d\+\ze<').'"'
>>
>> Let's say I use this command on the following text:
>> Table of Contents 5
>>
Patch 7.3.1019
Problem:These do not work with the new regexp engine: \%o123, \%x123,
\%d123, \%u123 and \%U123.
Solution: Implement these items.
Files: src/regexp_nfa.c
*** ../vim-7.3.1018/src/regexp_nfa.c2013-05-25 21:18:30.0 +0200
--- src/regexp_nfa.c2013
Patch 7.3.1018
Problem:New regexp engine wastes memory.
Solution: Allocate prog with actual number of states, not estimated maximum
number of sates.
Files: src/regexp_nfa.c
*** ../vim-7.3.1017/src/regexp_nfa.c2013-05-25 20:19:45.0 +0200
--- src/regexp_nfa.c
# HG changeset patch
# User ZyX
# Date 1369507217 -14400
# Node ID 72a773f3fc682f63c79d1b8481626fdec3198ddd
# Parent 8144426a1ffd077f23443e7de9e7c7c102395e6c
Add Py_TPFLAGS_HAVE_GC flag to types with tp_traverse+tp_clear
diff -r 8144426a1ffd -r 72a773f3fc68 src/if_py_both.h
--- a/src/if_py_both.
Patch 7.3.1017
Problem:Zero width match changes length of match.
Solution: For a zero width match put new states in the current position in
the state list.
Files: src/regexp_nfa.c, src/testdir/test64.in, src/testdir/test64.ok,
src/regexp.h
*** ../vim-7.3.1016/s
On Sat, May 25, 2013 at 1:13 PM, Bram Moolenaar wrote:
> Did you also check for correctness? It's easy to make a regexp engine
> that's fast but wrong. And do they possibly run out of memory and
> crash? I rewrote the original Vim regexp engine to be iterative instead
> of recursive to handle t
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 137 by zulolox4...@gmail.com: Memory fault-coredump unix aix
http://code.google.com/p/vim/issues/detail?id=137
What steps will reproduce the problem?
1.Edit a text file with 25000 lignes, about 3200 chars length every line
2.S
# HG changeset patch
# User ZyX
# Date 1369504060 -14400
# Node ID 8144426a1ffd077f23443e7de9e7c7c102395e6c
# Parent d85c9583a4c924cfc80b2816c4fc3605a592e746
Fix IterIter function
diff -r d85c9583a4c9 -r 8144426a1ffd src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 17:47:19 2013 +0400
+++ b/s
On 2013-05-25, Marcin Szamotulski wrote:
> Dear Vim Dev,
>
> I have a proposition for a small but nice feature. Whenever I do
> diff & then diffo (or diffo!) some settings are lost, for example the
> foldmethod is always reset to manual. It would be nice if vim could
> restore fdm setting to wha
Elias Diem wrote:
> I get a compiler warning for regexp_nfa.c.
>
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/in
Updates:
Status: WontFix
Comment #1 on issue 136 by brammool...@gmail.com: vim sets filetype of
empty TeX file to plaintex instead of tex
http://code.google.com/p/vim/issues/detail?id=136
This works as expected.
See :help ft-tex-plugin
You will want to use
let g:tex_flavor = "latex"
Dear Vim Dev,
I have a proposition for a small but nice feature. Whenever I do
diff & then diffo (or diffo!) some settings are lost, for example the
foldmethod is always reset to manual. It would be nice if vim could
restore fdm setting to what it was set before doing the diff. I don't
have an
# HG changeset patch
# User ZyX
# Date 1369489639 -14400
# Node ID d85c9583a4c924cfc80b2816c4fc3605a592e746
# Parent 4070da40d25e86084109ed015fe943d75413d612
Fix some possible memory leaks
diff -r 4070da40d25e -r d85c9583a4c9 src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 18:04:33 2013 +040
# HG changeset patch
# User ZyX
# Date 1369490673 -14400
# Node ID 4070da40d25e86084109ed015fe943d75413d612
# Parent 3fc0fc7ae6b145f0b0b223a993fb15bc78681ce7
Fix typo in pyiter_to_tv
diff -r 3fc0fc7ae6b1 -r 4070da40d25e src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 18:02:17 2013 +0400
+++
# HG changeset patch
# User ZyX
# Date 1369490537 -14400
# Node ID 3fc0fc7ae6b145f0b0b223a993fb15bc78681ce7
# Parent eb95fd146cc21c49103af9ff9fcb250827b83ba4
Rename DICTKEY_GET_NOTEMPTY to DICTKEY_GET
DICTKEY_GET was not used anywhere
diff -r eb95fd146cc2 -r 3fc0fc7ae6b1 src/if_py_both.h
--- a/
# HG changeset patch
# User ZyX
# Date 1369490340 -14400
# Node ID eb95fd146cc21c49103af9ff9fcb250827b83ba4
# Parent 920b38ba610a4b9b874a18828a5b13c1a560a583
Rename d to dict and lookupDict to lookup_dict
diff -r 920b38ba610a -r eb95fd146cc2 src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 14
> Looks like I got this one three times, but I didn't see 2/?.
It is a problem in header: it is named here as “(1/?) Fix “invalid read”
valgrind errors”.
These three messages should contain the same data: first is hg export without
c.diff, second is c.diff without hg export (deleted from google
Patch 7.3.1016
Problem:Unused field in nfa_state.
Solution: Remove lastthread.
Files: src/regexp.h, src/regexp_nfa.c
*** ../vim-7.3.1015/src/regexp.h2013-05-19 19:16:25.0 +0200
--- src/regexp.h2013-05-25 15:23:33.0 +0200
***
*** 74,80
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 136 by ondrej.pla...@gmail.com: vim sets filetype of empty TeX
file to plaintex instead of tex
http://code.google.com/p/vim/issues/detail?id=136
What steps will reproduce the problem? // under Linux
1. $ touch empty.tex
2.
Patch 7.3.1015
Problem:New regexp engine: Matching composing characters is wrong.
Solution: Fix matching composing characters.
Files: src/regexp_nfa.c, src/testdir/test95.in, src/testdir/test95.ok
*** ../vim-7.3.1014/src/regexp_nfa.c2013-05-25 12:28:08.0 +0200
--- src/rege
Hello all,
I get a compiler warning for regexp_nfa.c.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
Glts wrote:
> there is simple but straightforward "Benchmark of Regex Libraries" at
> http://lh3lh3.users.sourceforge.net/reb.shtml
>
> I measured search durations for both regexp engines in Vim 7.3.1010,
> using the same regular expressions and the same data they used. I added
> one simpler tes
Christian Brabandt wrote:
> Hi Ein!
>
> On Fr, 24 Mai 2013, Ein Brown wrote:
>
> > Hi, I have encountered a bug where my folds become 'corrupted' and
> > unrecognized by vim. I looks like this is caused by using :move on a
> > closed fold under the right circumstances.
> >
> > The SO questi
Dominique Pelle wrote:
> Attached patch removes a useless
> duplicated line in regexp_nfa_.c.
Thanks!
--
"You're fired." (1980)
"You're laid off." (1985)
"You're downsized." (1990)
"You're rightsized." (1992)
(Scott Adams - The Dilbert principle)
/// Bram Mool
Dominique Pelle wrote:
> Attached patch fixes 3 typos in documentation.
Thanks!
--
An easy way to determine if you have enough teamwork to be doomed is simply to
measure how long it takes from the time you decide to go to lunch together
until the time you actually eat.
ZyX wrote:
> # HG changeset patch
> # User ZyX
> # Date 1369422662 -14400
> # Node ID e3fac877d315709055ffaec4cc32a5f971ef5e97
> # Parent 5a4995e468e158438a43ba6cb046a3bd79e022e4
> Fix debugging dynamic build
Looks like I got this one three times, but I didn't see 2/?.
--
Your company is do
# HG changeset patch
# User ZyX
# Date 1369479301 -14400
# Node ID 920b38ba610a4b9b874a18828a5b13c1a560a583
# Parent df22b77f9a4b8172c6b41745a42a0574ce907d14
Fix dir()
Python documentation says that __members__ attribute is deprecated since
python-2.2, but this does not make dir() work properly
# HG changeset patch
# User ZyX
# Date 1369474993 -14400
# Node ID df22b77f9a4b8172c6b41745a42a0574ce907d14
# Parent cc578271bc44d90911e71c3e0992772826e5e26c
Purge out more Py_BuildValue: now don’t use it for building strings
diff -r cc578271bc44 -r df22b77f9a4b src/if_py_both.h
--- a/src/if_py_
Py_BuildValue is an overkill when all you need is a simple string.
# HG changeset patch
# User ZyX
# Date 1369474993 -14400
# Node ID df22b77f9a4b8172c6b41745a42a0574ce907d14
# Parent cc578271bc44d90911e71c3e0992772826e5e26c
Purge out more Py_BuildValue: now don’t use it for building strings
di
# HG changeset patch
# User ZyX
# Date 1369474461 -14400
# Node ID cc578271bc44d90911e71c3e0992772826e5e26c
# Parent a71b70fc1b4ea887cc5361a13e43c0b594309593
Add error handling to VimToPython function
diff -r a71b70fc1b4e -r cc578271bc44 src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 13:20:
# HG changeset patch
# User ZyX
# Date 1369473652 -14400
# Node ID a71b70fc1b4ea887cc5361a13e43c0b594309593
# Parent e6465392bfef41fcb4c92e7ddc7bf842b096c4ab
Add {Buffer,TabPage,Window}.valid attributes
diff -r e6465392bfef -r a71b70fc1b4e src/if_py_both.h
--- a/src/if_py_both.h Sat May 25 12:4
> The change to move fclose() into nfa_print_state() doesn't work though.
Ah sorry, it was my mistake.
2013/5/25 Bram Moolenaar :
>
> Taro Muraoka wrote:
>
>> I wrote a patch to make NFA state dump more pretty.
>>
>> Before patch:
>>
>> > (11) NFA_MOPEN(0) (-991) (id=11)
>> > (10) NFA_SPLIT
Taro Muraoka wrote:
> I wrote a patch to make NFA state dump more pretty.
>
> Before patch:
>
> > (11) NFA_MOPEN(0) (-991) (id=11)
> > (10) NFA_SPLIT (-1024) (id=10)
> > ( 8) NFA_MOPEN(1) (-990) (id=8)
> > ( 7) NFA_SPLIT (-1024) (id=7)
> > ( 1) CHAR(f)
Patch 7.3.1014
Problem:New regexp state dump is hard to read.
Solution: Make the state dump more pretty. (Taro Muraoka)
Files: src/regexp_nfa.c
*** ../vim-7.3.1013/src/regexp_nfa.c2013-05-25 12:18:34.0 +0200
--- src/regexp_nfa.c2013-05-25 12:25:43.0 +0200
*
Taro Muraoka wrote:
> I have improved logging of NFA regexp engine.
>
> - refine macros for logging.
> - add comments for logging.
>
> Please check attached patch.
Thanks.
I'll change this a bit. I don't like writing any log file on an error.
--
Back off man, I'm a scientist.
Patch 7.3.1013
Problem:New regexp logging is a bit messy.
Solution: Consistently use #defines, add explanatory comment. (Taro Muraoka)
Files: src/regexp_nfa.c
*** ../vim-7.3.1012/src/regexp_nfa.c2013-05-24 23:10:45.0 +0200
--- src/regexp_nfa.c2013-05-25 12:17:35.00
# HG changeset patch
# User ZyX
# Date 1369471287 -14400
# Node ID e6465392bfef41fcb4c92e7ddc7bf842b096c4ab
# Parent bb61035bd1793db3e248f647092831275e7e0042
Fix dynamic compilation with python-2.3
python-2.2 dynamic build compiles as well, but because I failed to build so
library I cannot test
# HG changeset patch
# User ZyX
# Date 1369468858 -14400
# Node ID bb61035bd1793db3e248f647092831275e7e0042
# Parent f3a1f7c373ee941b71739260f72f6babbff6ce0f
Add possibility to assign to vim.Buffer.name
diff -r f3a1f7c373ee -r bb61035bd179 runtime/doc/if_pyth.txt
--- a/runtime/doc/if_pyth.txt
# HG changeset patch
# User ZyX
# Date 1369422662 -14400
# Node ID e3fac877d315709055ffaec4cc32a5f971ef5e97
# Parent 5a4995e468e158438a43ba6cb046a3bd79e022e4
Fix debugging dynamic build
diff -r 5a4995e468e1 -r e3fac877d315 src/if_python.c
--- a/src/if_python.c Fri May 24 23:10:50 2013 +0200
++
--
--
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" group.
To unsubs
# HG changeset patch
# User ZyX
# Date 1369465902 -14400
# Node ID f3a1f7c373ee941b71739260f72f6babbff6ce0f
# Parent e3fac877d315709055ffaec4cc32a5f971ef5e97
Fix invalid read errors:
defer DICTKEY_UNREF until key is no longer needed
diff -r e3fac877d315 -r f3a1f7c373ee src/if_py_both.h
--- a/sr
# HG changeset patch
# User ZyX
# Date 1369422662 -14400
# Node ID e3fac877d315709055ffaec4cc32a5f971ef5e97
# Parent 5a4995e468e158438a43ba6cb046a3bd79e022e4
Fix debugging dynamic build
diff -r 5a4995e468e1 -r e3fac877d315 src/if_python.c
--- a/src/if_python.c Fri May 24 23:10:50 2013 +0200
++
--
--
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" group.
To unsubs
Attached patch removes a useless
duplicated line in regexp_nfa_.c.
Regards
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 information, visit http://www.vim.org/maillist.php
---
You received t
On Sat, May 25, 2013 at 1:43 AM, glts <676c7...@gmail.com> wrote:
> On Sat, May 25, 2013 at 1:17 AM, Marc Weber wrote:
>> Starting vim takes less than a second, your runs are > 10 sec most of
>> the time, so I guess that re=1 vs re=2 is representative for your cases.
>
> Vim startup time is <0.01s
Hi
Attached patch fixes 3 typos in documentation.
Regards
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 information, visit http://www.vim.org/maillist.php
---
You received this message beca
48 matches
Mail list logo
