On 05-Jun-2013 08:03 +0200, Christian Brabandt wrote:
> [...] the old engine has an long standing bug with \%V ;(
>
> e.g:
>
> vim -u NONE -N
> ifoobar
> 0ve
> /\%Vfoobar\%V
>
> I should have probably provided a fix long ago.
Where is the bug, that there's no match?! That's intended, as the la
On Tue, June 4, 2013 18:29, Bram Moolenaar wrote:
>
> Patch 7.3.1112
> Problem:New regexp engine: \%V not supported.
> Solution: Implement \%V. Add tests.
> Files:src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
> src/testdir/test64.ok
The good thing about this i
On Wed, June 5, 2013 00:14, Tony Mechelynck wrote:
> On 31/05/13 15:31, A. S. Budden wrote:
>>> When using cscope, the path as provided to the "cs add" command is
>>> used. If the working directory changes, this is potentially no longer
>>> valid. This causes me a problem as I have a plugin that
On Wednesday, June 5, 2013 6:58:22 AM UTC+3, ZyX wrote:
> Ah, I missed these dots. But still the OP says that with those two dots `foo`
> is highlighted and not `fo`.
No, I also missed the two dots!
I compared "foo\&" with "\(foo\)\@=". So, "never mind", I guess...
--
--
You received this
среда, 5 июня 2013 г., 4:01:33 UTC+4 пользователь Ken Takata написал:
> Hi,
>
> 2013/06/05 Wed 4:47:42 UTC+9 ZyX wrote:
> > os.fchdir does not exist there. And vim.*chdir is similar to posix.chdir:
> > you are not supposed to use this directly, but it holds implementation of
> > functions in os.
> The trailing '..' in both examples is important. I get the same
> highlighting ('fo') with either of:
Ah, I missed these dots. But still the OP says that with those two dots `foo`
is highlighted and not `fo`.
> /foo\&..
> and
> /\(foo\)\@=..
>
> In both vim 7.3.266 and 7.3.1115 (with both
On Tue, 4 Jun 2013, Ron Aaron wrote:
On Tuesday, June 4, 2013 11:30:09 PM UTC+3, ZyX wrote:
`\(foo\)\@=` highlights f and matches zero-width as expected. If on
your system it does something else it is a bug.
Once again, the help states:
Note that using "\&" works the same as using
1. ":set guifont=Cousine\ 10" is only for gvim with GTK2 GUI. On Windows,
AFAIK that can only exist for running under Cygwin X11 with the Cygwin DLL.
For "native" Windows (running with no help of Cygwin or X11), you should
use ":set guifont=Cousine:h10:cDEFAULT".
2. You should set 'guifont' in you
On Tuesday, June 4, 2013 11:30:09 PM UTC+3, ZyX wrote:
> `\(foo\)\@=` highlights f and matches zero-width as expected. If on your
> system it does something else it is a bug.
Once again, the help states:
Note that using "\&" works the same as using "\@=": "foo\&.." is the
same
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, apart
from the fact, that entries from viminfo versions older than the previous one
are mi
Hi,
2013/06/05 Wed 4:47:42 UTC+9 ZyX wrote:
> os.fchdir does not exist there. And vim.*chdir is similar to posix.chdir: you
> are not supposed to use this directly, but it holds implementation of
> functions in os.* in case somebody needs this. Even tests are using os.*, not
> vim.*.
Now I und
i like this patch
在 2013-6-5 上午3:42，"Bram Moolenaar" 写道：
>
> Skeept wrote:
>
> > On Monday, April 15, 2013 6:49:57 AM UTC-5, Bram Moolenaar wrote:
> > > Lech Lorens wrote:
> > >
> > >
> > > > On 13-Apr-2013 Bram Moolenaar wrote:
> > > > > Thanks. Thus only when ~/.vimrc does not exist then ~/.vim
Excerpts from ZyX ZyX's message of Wed Jun 05 00:00:31 +0200 2013:
> This is the intention. Not building something into vim leads to creating
> bicycles by plugin authors. And I never saw anybody using functions defined
> in vim runtime files (except for vimball support in VAM). There must be a
> r
On 31/05/13 15:31, A. S. Budden wrote:
Forwarding to vim-dev as requested... any cscope/vim experts here?
Al
-- Forwarded message --
From: Bram Moolenaar
Date: 22 May 2013 22:02
Subject: Re: Bug: cscope interface should use absolute paths
To: A. S. Budden
Al -
When using csco
On Jun 5, 2013 1:22 AM, "Marc Weber" wrote:
>
> You've been missing documenting default settings ..
>
> > Does not run ``&pythoninstallprg`` if bang was specified.
> May be counter intuitive. ! usually means "force it".
> I understand the idea "make things work by default".
> But i think it sh
On 04/06/13 23:05, Dominique Pellé wrote:
Tony Mechelynck wrote:
After about two weeks AFK, downloaded 7.3 patches 981 to 1115 (and
intervening runtime changes), tried to compile (full build, "make
reconfig").
Tiny build fails as follows:
[...]
Attached patch should fix the 'tiny' build +
David,
Thank you for your kind series of notes. Since I have lived with unix or its
variants for a long time (my first windows98 machine was taken over by Linux in
a week), I've never set file format explicitly to send emails to the list. Now
I'm using MacOS X 10.8.3 and find myself in troubl
You've been missing documenting default settings ..
> Does not run ``&pythoninstallprg`` if bang was specified.
May be counter intuitive. ! usually means "force it".
I understand the idea "make things work by default".
But i think it should be the user having the choice anyway.
> > - where i
Tony Mechelynck wrote:
> After about two weeks AFK, downloaded 7.3 patches 981 to 1115 (and
> intervening runtime changes), tried to compile (full build, "make
> reconfig").
>
> Tiny build fails as follows:
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
> -fno-strength-reduce -
On 2013-06-04, Bram Moolenaar wrote:
> Skeept wrote:
>
> > On Monday, April 15, 2013 6:49:57 AM UTC-5, Bram Moolenaar wrote:
> > > Lech Lorens wrote:
> > >
> > >
> > > > On 13-Apr-2013 Bram Moolenaar wrote:
> > > > > Thanks. Thus only when ~/.vimrc does not exist then ~/.vim/vimrc will
> > > >
After about two weeks AFK, downloaded 7.3 patches 981 to 1115 (and
intervening runtime changes), tried to compile (full build, "make
reconfig").
Tiny build fails as follows:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_
...
> Yes the update fixed the problems. You saved it with Windows line endings
>> again though.
>>
>> I apologize to you for getting you into trouble again. Though the file
>> itself is in unix format and I double-checked not to send window-friendly
>> attachments, my Mail did something unnecess
вторник, 4 июня 2013 г., 16:53:58 UTC+4 пользователь Ron Aaron написал:
> Aha. OK, I thought it would match "foo" like the \@= does (e.g. that
> highlights the foo). The help is not clear, then.
`\(foo\)\@=` highlights f and matches zero-width as expected. If on your system
it does something e
вторник, 4 июня 2013 г., 17:16:33 UTC+4 пользователь 依云 написал:
> In Vim version <= 7.3.1031, the following code works and finds the
> correct function:
>
> :echo function('138_JumpToEndForward')
>
> Of course, change '138_JumpToEndForward' to some 's:' prefixed function
> Vim knows.
>
> With V
Patch 7.3.1115
Problem:Many users don't like the cursor line number when 'relativenumber'
is set.
Solution: Have four combinations with 'number' and 'relativenumber'.
(Christian Brabandt)
Files: runtime/doc/options.txt, src/option.c, src/screen.c,
src
I sent the original email only to Christian Wellenbrock. So here is a copy...
Begin forwarded message:
> From: Kazunobu Kuriyama
> Subject: Re: [RFC] Revision of Objective-C Syntax
> Date: June 5, 2013 5:04:24 AM GMT+09:00
> To: Christian Wellenbrock
>
> On Jun 5, 2013, at 3:41 AM, Christian
2013/6/4 Kazunobu Kuriyama
> On Jun 5, 2013, at 3:41 AM, Christian Wellenbrock <
> christian.wellenbr...@gmail.com> wrote:
>
> >
> > Yes the update fixed the problems. You saved it with Windows line
> endings again though.
>
> I apologize to you for getting you into trouble again. Though the fi
On 4 June 2013, Bram Moolenaar wrote:
>
> lcd wrote:
>
> > On 4 June 2013, Bram Moolenaar wrote:
> > >
> > > I wrote:
> > >
> > > > Patch 7.3.1110
> > > > Problem:New regexp matching: Using \@= and the like can be slow.
> > > > Solution: Decide whether to first try matching the zero-wdi
вторник, 4 июня 2013 г., 1:57:55 UTC+4 пользователь Ken Takata написал:
> Hi,
>
> 2013/06/03 Mon 21:01:27 UTC+9 Ken Takata wrote:
> > There is still another problem on Windows.
> > The following commands cause a crash:
> >
> > :py import vim
> > :py vim.fchdir()
> >
> > I think NULL check of _ch
Skeept wrote:
> On Monday, April 15, 2013 6:49:57 AM UTC-5, Bram Moolenaar wrote:
> > Lech Lorens wrote:
> >
> >
> > > On 13-Apr-2013 Bram Moolenaar wrote:
> > > > Thanks. Thus only when ~/.vimrc does not exist then ~/.vim/vimrc will
> > > > be used. That should work for places where a new Vi
Patch 7.3.1114 (after 7.3.1110)
Problem:Can't build without the syntax feature.
Solution: Add #ifdefs. (Erik Falor)
Files: src/regexp_nfa.c
*** ../vim-7.3.1113/src/regexp_nfa.c2013-06-04 21:27:33.0 +0200
--- src/regexp_nfa.c2013-06-04 21:39:30.0 +0200
*
lcd wrote:
> On 4 June 2013, Bram Moolenaar wrote:
> >
> > I wrote:
> >
> > > Patch 7.3.1110
> > > Problem:New regexp matching: Using \@= and the like can be slow.
> > > Solution: Decide whether to first try matching the zero-wdith part or
> > > what
> > > follows, whatever is mor
Erik Falor wrote:
> regexp_nfa.c cannot compile because the following macros are undefined
> when features =3D small|tiny:
>
> NFA_ZOPEN
> NFA_ZOPEN9
> NFA_ZCLOSE
> NFA_ZCLOSE9
>
> These macros are protected by #ifdef FEAT_SYN_HL beginning at line 116
> in the same file.
>
> The functions fail
вторник, 4 июня 2013 г., 10:59:06 UTC+4 пользователь MarcWeber написал:
> Excerpts from ZyX ZyX's message of Tue Jun 04 05:55:18 +0200 2013:
> > I am no longer seeing why automatic sourcing of any python file from any
> > directory should exist in case loadpyplugin() is implemented.
>
> It would b
Patch 7.3.1113
Problem:New regexp engine: \%'m not supported.
Solution: Implement \%'m. Add tests.
Files: src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
src/testdir/test64.ok
*** ../vim-7.3.1112/src/regexp.c2013-06-04 18:28:45.0 +0200
--- src/regex
On 4 June 2013, Bram Moolenaar wrote:
>
> I wrote:
>
> > Patch 7.3.1110
> > Problem:New regexp matching: Using \@= and the like can be slow.
> > Solution: Decide whether to first try matching the zero-wdith part or what
> > follows, whatever is more likely to fail.
> > Files:
On Tuesday, June 4, 2013 7:39:33 PM UTC+2, Kazunobu Kuriyama wrote:
> Hi, Christian,
>
>
>
> Thank you for your prompt feedback. The picture with the source code was
> awfully helpful to find and fix the problems. Hopefully, the attached
> version should fix the problems you pointed out, at
On 4 June 2013, Gary Johnson wrote:
> On 2013-06-04, Ron Aaron wrote:
> > I understand.
> >
> > But if you were to do that, you would really also have to update the
> > 'vim.org' site which says where the patches are, etc.
> >
> > I use a script to grab the latests patches: it sees what patchlev
On Monday, April 15, 2013 6:49:57 AM UTC-5, Bram Moolenaar wrote:
> Lech Lorens wrote:
>
>
>
> > On 13-Apr-2013 Bram Moolenaar wrote:
>
> > > Thanks. Thus only when ~/.vimrc does not exist then ~/.vim/vimrc will
>
> > > be used. That should work for places where a new Vim is installed. For
regexp_nfa.c cannot compile because the following macros are undefined
when features = small|tiny:
NFA_ZOPEN
NFA_ZOPEN9
NFA_ZCLOSE
NFA_ZCLOSE9
These macros are protected by #ifdef FEAT_SYN_HL beginning at line 116
in the same file.
The functions failure_chance() and nfa_regmatch() make unguarded
Hi, Christian,
Thank you for your prompt feedback. The picture with the source code was
awfully helpful to find and fix the problems. Hopefully, the attached version
should fix the problems you pointed out, at least for the given part of the
code.
KK
On Jun 4, 2013, at 11:51 PM, Christian W
Am 04.06.2013 17:32, schrieb Andy Wokula:
Am 04.06.2013 15:16, schrieb lilydjwg:
In Vim version <= 7.3.1031, the following code works and finds the
correct function:
:echo function('138_JumpToEndForward')
Of course, change '138_JumpToEndForward' to some 's:' prefixed function
Vim knows.
With
Patch 7.3.1112
Problem:New regexp engine: \%V not supported.
Solution: Implement \%V. Add tests.
Files: src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
src/testdir/test64.ok
*** ../vim-7.3./src/regexp.c2013-06-03 19:41:01.0 +0200
--- src/regexp.
On 2013-06-04, Ron Aaron wrote:
> I understand.
>
> But if you were to do that, you would really also have to update the
> 'vim.org' site which says where the patches are, etc.
>
> I use a script to grab the latests patches: it sees what patchlevel
> I'm at, and then scans the ftp site for any la
> Go forward to 7.3.1110, should be better.
Seems all good now, thanks!
--
--
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 b
fun! Dummy()
let g:test = 1
augroup RESIZE
autocmd VimResized * if g:test == 1 | let g:test =2 | endif
augroup end
for j in range(0,200)
for i in range(0,5000)
let x = 7
endfor
endfor
echoe g:test
let g:test = 0
endf
What do I expect? If I run "my viml" code I ex
I understand.
But if you were to do that, you would really also have to update the
'vim.org' site which says where the patches are, etc.
I use a script to grab the latests patches: it sees what patchlevel I'm
at, and then scans the ftp site for any later-numbered patches,
downloads and appli
Patch 7.3.
Problem:nfa_recognize_char_class() implementation is inefficient.
Solution: Use bits in an int instead of chars in a string. (Dominique Pelle)
Files: src/regexp_nfa.c, src/testdir/test36.in, src/testdir/test36.ok
*** ../vim-7.3.1110/src/regexp_nfa.c2013-06-04 14:23:
Am 04.06.2013 15:16, schrieb lilydjwg:
In Vim version <= 7.3.1031, the following code works and finds the
correct function:
:echo function('138_JumpToEndForward')
Of course, change '138_JumpToEndForward' to some 's:' prefixed function
Vim knows.
With Vim version >= 7.3.1071, it returns a strin
Ron Aaron wrote:
> Er, but all the patches up until this last have appeared on the ftp
> site. I thought that was the canonical patch place.
Recently there was a discussion about git and all its features.
It's good to know at least some people just use patches.
It's just that sometimes I get
Omoikane wrote:
> As of 7.3.1088, VIM and GVIM appears to have gotten very slow at
> redrawing files with syntax highlighting. This regression only
> happened as of 7.3.1088, 7.3.1087 and earlier seem to redraw at
> regular speed. Please take a look?
>
> To reproduce:
> 1. Recompile VIM and in
On Tuesday, June 4, 2013 4:33:11 PM UTC+2, Christian Wellenbrock wrote:
> On Tuesday, June 4, 2013 4:27:49 PM UTC+2, David Fishburn wrote:
>
> > ...>
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > > "AdjustIo.h" 81L, 2743C
>
> >
>
> > > Error detected while processing /usr/share/vim/vim
Er, but all the patches up until this last have appeared on the ftp
site. I thought that was the canonical patch place.
On 06/04/2013 05:26 PM, Bram Moolenaar wrote:
Ron Aaron wrote:
it doesn't appear yet on the ftp site
I thought everybody was using the Mercurial repository.
I'll push the
Adnan Zafar wrote:
> On Sun, Jun 2, 2013 at 5:09 PM, Bram Moolenaar wrote:
>
> > Thanks. This is tricky stuff, can you please add a test?
> > One that partly fails before this patch.
> > I know that's not easy, but manually testing this is also
> > not a good idea.
> > It's OK if the test only
Ron Aaron wrote:
> it doesn't appear yet on the ftp site
I thought everybody was using the Mercurial repository.
I'll push the patch to the ftp site as well.
--
hundred-and-one symptoms of being an internet addict:
82. AT&T names you Customer of the Month for the third consecutive time.
//
For those who aren't familiar with ^M at EOL ;-). Hopefully, this will work
for you.
Sorry for your inconvenience.
--
--
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/m
On Tuesday, June 4, 2013 4:27:49 PM UTC+2, David Fishburn wrote:
> ...>
>
>
>
>
>
>
> > "AdjustIo.h" 81L, 2743C
>
> > Error detected while processing /usr/share/vim/vim73/syntax/objc.vim:
>
> > line 6:
>
> > E492: Not an editor command: ^M
>
> > line 8:
>
> > E15: Invalid expressio
...>
> > "AdjustIo.h" 81L, 2743C
> > Error detected while processing /usr/share/vim/vim73/syntax/objc.vim:
> > line6:
> > E492: Not an editor command: ^M
> > line8:
> > E15: Invalid expression: exists("b:current_syntax")^M
> > line 107:
> > E488: Trailing characters
> > line 110:
> > E17
it doesn't appear yet on the ftp site
--
--
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
On Jun 4, 2013 5:34 PM, "Christian Wellenbrock" <
christian.wellenbr...@gmail.com> wrote:
>
> On Tuesday, June 4, 2013 3:12:20 PM UTC+2, Kazunobu Kuriyama wrote:
> > Hi,
> >
> >
> >
> > I'm the maintainer of the Objective-C syntax file, syntax/objc.vim. As
the new features that have been added to
On Tuesday, June 4, 2013 3:12:20 PM UTC+2, Kazunobu Kuriyama wrote:
> Hi,
>
>
>
> I'm the maintainer of the Objective-C syntax file, syntax/objc.vim. As the
> new features that have been added to the language for years appear to become
> stable and have passed the point of no return (really?)
As of 7.3.1088, VIM and GVIM appears to have gotten very slow at
redrawing files with syntax highlighting. This regression only
happened as of 7.3.1088, 7.3.1087 and earlier seem to redraw at
regular speed. Please take a look?
To reproduce:
1. Recompile VIM and include all patches up to and incl
In Vim version <= 7.3.1031, the following code works and finds the
correct function:
:echo function('138_JumpToEndForward')
Of course, change '138_JumpToEndForward' to some 's:' prefixed function
Vim knows.
With Vim version >= 7.3.1071, it returns a string like
'<80>R138_JumpToEndForward' and th
Hi,
I'm the maintainer of the Objective-C syntax file, syntax/objc.vim. As the new
features that have been added to the language for years appear to become stable
and have passed the point of no return (really?), I'm now thinking of revising
the syntax file completely for the sake of the "Mode
I wrote:
> Patch 7.3.1110
> Problem:New regexp matching: Using \@= and the like can be slow.
> Solution: Decide whether to first try matching the zero-wdith part or what
> follows, whatever is more likely to fail.
> Files:src/regexp_nfa.c
This should make syntax highl
Aha. OK, I thought it would match "foo" like the \@= does (e.g. that
highlights the foo). The help is not clear, then.
On Tuesday, June 4, 2013 3:48:54 PM UTC+3, Andy Wokula wrote:
> Not a bug -- it matches where "foo" matches with zero width ("f" is
> highlighted but not matched).
--
--
Yo
Am 04.06.2013 14:36, schrieb Ron Aaron:
The help says:
Note that using "\&" works the same as using "\@=": "foo\&.." is the
same as "\(foo\)\@=..". But using "\&" is easier, you don't need the
braces.
However, if you look for "foo\&", it only matches "f" and not "foo".
Tried
The help says:
Note that using "\&" works the same as using "\@=": "foo\&.." is the
same as "\(foo\)\@=..". But using "\&" is easier, you don't need the
braces.
However, if you look for "foo\&", it only matches "f" and not "foo". Tried
with both re=1 and re=2.
--
--
Patch 7.3.1110
Problem:New regexp matching: Using \@= and the like can be slow.
Solution: Decide whether to first try matching the zero-wdith part or what
follows, whatever is more likely to fail.
Files: src/regexp_nfa.c
*** ../vim-7.3.1109/src/regexp_nfa.c2013-06-03 1
On Tue, Jun 04, 2013 at 11:18:49AM +0200, Bram Moolenaar wrote:
> Ben Fritz wrote:
> > On Sunday, June 2, 2013 3:36:54 PM UTC-5, Grant Farnsworth wrote:
> > > > - ":set nonu nornu" means: I don't want any line numbers;
> > > > - ":set nu nornu" means: I want to see only absolute numbers;
> > > >
On 03/06/2013 18:42, Marc Weber wrote:
Excerpts from Mike Williams's message of Mon Jun 03 18:11:34 +0200 2013:
o remotes and tracking anonymous branches
The equivalent to remotes would be to add new path aliases to the repo's
.hgrc file under [paths]. See `hg help paths` for more details on th
Ben Fritz wrote:
> On Sunday, June 2, 2013 3:36:54 PM UTC-5, Grant Farnsworth wrote:
> > > - ":set nonu nornu" means: I don't want any line numbers;
> > > - ":set nu nornu" means: I want to see only absolute numbers;
> > > - ":set nonu rnu" means: I want to see only relative numbers;
> > > - ":se
Marc Weber wrote:
> Wired things which I think can happen:
> 1) run a viml loop
> 2) resize the window
>
> while viml is in a loop it calls line_breakcheck which in turn calls
> ui_breakcheck which calls gui_mch_update which can recieve resize events
> which can trigger an au command which can d
Dominique Pelle wrote:
> Bram Moolenaar wrote:
>
> >
> > Ron Aaron wrote:
> >
> >> I'm sure there's a reason, but I wonder:
> >>
> >> why, in regexp_nfa.c "nfa_recognize_char_class()", is the "config"
> >> using chars instead of integer bitmaps? I would expect bitmaps to be
> >> faster (as wel
On 3 June 2013 17:25, Christian Brabandt wrote:
> On Mon, June 3, 2013 18:07, abud...@gmail.com wrote:
>> Certainly looks promising: what do you think are the chances of getting
>> this into Vim 7.4?
>
> Looks pretty good I would say. From the latest todo list in the
> repository:
>
> Patch to sto
Wired things which I think can happen:
1) run a viml loop
2) resize the window
while viml is in a loop it calls line_breakcheck which in turn calls
ui_breakcheck which calls gui_mch_update which can recieve resize events
which can trigger an au command which can disturb your initial loop ?
I woul
76 matches
Mail list logo
