Hi,
When I use #if 1 ... #endif in C, spell checking works incorrectly.
Here is an example: c-vim_before.png.
Spell checking is enabled inside #if 1, and disabled inside #if 0.
Attached patch fixes this. (see c-vim_after.png)
Best regards,
Ken Takata
--
--
You received this message from the "
2013 m. gegužė 31 d., penktadienis 23:15:07 UTC+3, Bram Moolenaar rašė:
> Patch 7.3.1083
>
> Problem:New regexp engine: Does not support \%^ and \%$.
>
> Solution: Support matching start and end of file.
With this patch applied and using Python syntax script from
http://www.vim.org/script
Hi all.
Currently, vim's jumplist keeps all jump marks, but I think the modern way
is trim jump marks if necessary. For example:
1
2
>3
4
Now insert mark 5, it will become:
1
2
3
4
5
>
But, if I want to jump back to mark 1, I need to press too many ,
so I make a path to change this. Afte
On Sat, Jun 01, 2013 at 05:44:17AM +0200, Marc Weber wrote:
j And third, you must not use the same code as :pyfile. It is already
bad that somebody may think that creating large file sourced using
:pyfile is a good idea: it is never a good idea because file executed
via :pyfile is executed as a
Patch 7.3.1085
Problem:New regexp engine: Non-greedy multi doesn't work.
Solution: Implement \{-}.
Files: src/regexp_nfa.c, src/testdir/test64.in, src/testdir/test64.ok
*** ../vim-7.3.1084/src/regexp_nfa.c2013-05-31 23:17:56.0 +0200
--- src/regexp_nfa.c2013-06-01 12:22
Ken Takata wrote:
> When I use #if 1 ... #endif in C, spell checking works incorrectly.
> Here is an example: c-vim_before.png.
> Spell checking is enabled inside #if 1, and disabled inside #if 0.
>
> Attached patch fixes this. (see c-vim_after.png)
Thanks, I'll include it.
--
He who laughs l
Audrius Kažukauskas wrote:
> 2013 m. gegužė 31 d., penktadienis 23:15:07 UTC+3, Bram Moolenaar rašė:
> > Patch 7.3.1083
> >
> > Problem:New regexp engine: Does not support \%^ and \%$.
> >
> > Solution: Support matching start and end of file.
>
> With this patch applied and using Python
Patch 7.3.1086
Problem:Old regexp engine accepts illegal range, new one doesn't.
Solution: Also accept the illegal range with the new engine.
Files: src/regexp_nfa.c, src/testdir/test64.in, src/testdir/test64.ok
*** ../vim-7.3.1085/src/regexp_nfa.c2013-06-01 12:40:14.0 +02
2013 m. birželis 1 d., šeštadienis 14:24:39 UTC+3, Bram Moolenaar rašė:
> I don't see an error when opening a Python file.
> So what is in that line of your python.vim?
> The URL you gave doesn't work. Must be this one:
>
> http://www.vim.org/scripts/script.php?script_id=790
>
> The problem appe
Marco Hinz wrote:
> I just noticed a little glitch when I looked at :version
>
> --- a/src/version.c Thu May 30 22:44:02 2013 +0200
> +++ b/src/version.c Fri May 31 17:19:56 2013 +0200
> @@ -250,1 +250,1 @@
> - "+fork()",
> + "+fork",
>
It was there intentionally. Does it cause a
Patch 7.3.1087
Problem:A leading star is not seen as a normal char when \{} follows.
Solution: Save and restore the parse state properly.
Files: src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
src/testdir/test64.ok
*** ../vim-7.3.1086/src/regexp.c2013-05-29
On Jun 1, 2013 7:43 AM, "Marc Weber" wrote:
>
> ZyX: Usually you're rigth with what you're saying.
> So please help find the best forum to place your "style guides" about
> "how to write unobstrusive perfect python based vim plugins".
>
> You all know that I've introduced this wiki:
> http://vim-w
Hi,
I noticed that test86 and test87 fail on Windows. (Vim 7.3.1087)
Here is the result of test86:
< p/gopts1: '.,,'
---
> p/gopts1: '.,/usr/include,,'
344c344
< testdir\foo
---
> testdir/foo
347c347
< testdir\bar
---
> testdir/bar
350c350
< testdir\test86.in
---
> testdir/test86.in
and the
# HG changeset patch
# User ZyX
# Date 1370101974 -14400
# Branch python-extended-4
# Node ID f37c4b0b09f688698e23d14c6f915968d0868523
# Parent 0921ff181087b318c2322ab5af06758776a59bd1
Fix platform-specific stuff in tests
diff -r 0921ff181087 -r f37c4b0b09f6 src/testdir/test86.in
--- a/src/testd
--
--
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
* I am listing all unapplied patches here.
# HG changeset patch
# User ZyX
# Date 1369975224 -14400
# Branch python-extended-4
# Node ID 0921ff181087b318c2322ab5af06758776a59bd1
# Parent 2eb30f341e8d418c2bbcd476722133db840db167
Add missing documentation
diff -r 2eb30f341e8d -r 0921ff181087 runt
# HG changeset patch
# User ZyX
# Date 1370101974 -14400
# Branch python-extended-4
# Node ID f37c4b0b09f688698e23d14c6f915968d0868523
# Parent 0921ff181087b318c2322ab5af06758776a59bd1
Fix platform-specific stuff in tests
diff -r 0921ff181087 -r f37c4b0b09f6 src/testdir/test86.in
--- a/src/testd
# HG changeset patch
# User ZyX
# Date 1370092920 -14400
# Branch python-extended-4
# Node ID 0ee8bb6bd07f29fd51c7b753492ac727b69ac7ae
# Parent f37c4b0b09f688698e23d14c6f915968d0868523
More possible memory leak fixes
diff -r f37c4b0b09f6 -r 0ee8bb6bd07f src/if_py_both.h
--- a/src/if_py_both.h S
Is a replacement for @Xavier de Gaye patch written in C. Main idea is the same.
# HG changeset patch
# User ZyX
# Date 1370102113 -14400
# Branch python-extended-4
# Node ID 807b755f9898d68e4d93f18e7964783b207826b2
# Parent 0ee8bb6bd07f29fd51c7b753492ac727b69ac7ae
Add vim.chdir and vim.fchdir fu
# HG changeset patch
# User ZyX
# Date 1370102113 -14400
# Branch python-extended-4
# Node ID 807b755f9898d68e4d93f18e7964783b207826b2
# Parent 0ee8bb6bd07f29fd51c7b753492ac727b69ac7ae
Add vim.chdir and vim.fchdir functions, record them as attributes of os module
diff -r 0ee8bb6bd07f -r 807b755f
https://github.com/vim-scripts/taglist.vim
There are several pull requests (A version update is also present)
Who owns and maintains these scripts in the github ?
--
Thanks & Regards,
R Ashwin Sathya
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your repl
On 01-Jun-2013 18:34 +0200, ashwin sathya wrote:
> https://github.com/vim-scripts/taglist.vim
>
>
> There are several pull requests (A version update is also present)
> Who owns and maintains these scripts in the github ?
The mirrors on http://vim-scripts.org/ are not necessarily monitored by
t
Patch 7.3.1088
Problem:New regexp engine: \@<= and \@rs_scan);
if (REG_MULTI)
{
! if (rp->rs_un.regsave.rs_u.pos.col == 0)
{
if (rp->rs_un.regsave.rs_u.pos.lnum
Hi Bram,
> It was there intentionally. Does it cause a problem anywhere?
Oh, not at all. But it seemed inconsistent because ":h +feature-list"
lists the feature as "+fork", but :version shows "+fork()".
That could mislead people to use code like "has('fork()')".
--
--
You received this mess
ZyX wrote:
> # HG changeset patch
> # User ZyX
> # Date 1370101974 -14400
> # Branch python-extended-4
> # Node ID f37c4b0b09f688698e23d14c6f915968d0868523
> # Parent 0921ff181087b318c2322ab5af06758776a59bd1
> Fix platform-specific stuff in tests
Thanks for the quick response!
--
You have th
Patch 7.3.1089
Problem:Tests 86 and 87 fail on MS-Windows. (Ken Takata)
Solution: Fix platform-specific stuff. (ZyX)
Files: src/testdir/test86.in, src/testdir/test86.ok,
src/testdir/test87.in, src/testdir/test87.ok
*** ../vim-7.3.1088/src/testdir/test86.in 2013-05-31
Hi,
On Sat, Jun 1, 2013 at 9:34 AM, ashwin sathya wrote:
>
> https://github.com/vim-scripts/taglist.vim
>
> There are several pull requests (A version update is also present)
> Who owns and maintains these scripts in the github ?
>
I released version 4.6 of the taglist plugin few months ago. The
On 01-Jun-2013 20:50 +0200, Yegappan Lakshmanan wrote:
> I released version 4.6 of the taglist plugin few months ago. The Git hub
> repository has the 4.5 version. I don't know who is the owner of the
> Github vim-scripts repository.
I thinks it's more or less two guys; you can contact / open iss
# HG changeset patch
# User ZyX
# Date 1370096560 -14400
# Branch python-extended-4
# Node ID f322321a58b1a500736527ea82627fd65b2954bb
# Parent 807b755f9898d68e4d93f18e7964783b207826b2
Add vim.version and vim.version_info
diff -r 807b755f9898 -r f322321a58b1 runtime/doc/if_pyth.txt
--- a/runtime
Hi,
I have downloaded the sources from there. Thanks for the update.
The reasoning behind my query is the fact that i am extensively using
vundle to manage the plugins.
On Sat, Jun 1, 2013 at 11:50 AM, Yegappan Lakshmanan wrote:
> Hi,
>
> On Sat, Jun 1, 2013 at 9:34 AM, ashwin sathya
> wrote:
Patch 7.3.1090
Problem:New regexp engine does not support \z1 .. \z9 and \z(.
Solution: Implement the syntax submatches.
Files: src/regexp.h, src/regexp_nfa.c
*** ../vim-7.3.1089/src/regexp.h2013-05-30 17:05:34.0 +0200
--- src/regexp.h2013-06-01 22:18:07.00
Excerpts from ashwin sathya's message of Sat Jun 01 22:56:38 +0200 2013:
> vundle to manage the plugins.
Get started with vim-addon-manager and your problems are gone because
- it honors authors upstreams
- it fetches most recent plugins from vim.sf.net, not form a mirror.
I still want to see vim-
I wrote:
> Patch 7.3.1090
> Problem:New regexp engine does not support \z1 .. \z9 and \z(.
> Solution: Implement the syntax submatches.
> Files:src/regexp.h, src/regexp_nfa.c
Sorry for the unfinished subject...
Syntax highlighting of XML with long lines is a lot faster now.
-
I've been thinking about what's causing trouble to me.
Lack of workflows - lack of documentation.
http://vim.sourceforge.net/ -> download -> patch
No hint about how patches should be submitted.
No hinting about release cycles
NO hinting about how to manage vim source and patches.
I'm used to git.
@ZyX: I totally agree on plugin/ being a bad choice. And I also agree
that the patch is not perfect. I had to get it out due to Brams deadline
(Friday) - because otherwise much worse things could have happened -
people starting to use if py2 then .. else .. code which you cannot get
rid of.
I also
give cscope full path
$ find `pwd` | cscope -i -
On Friday, May 31, 2013 3:41:05 PM UTC+8, A. S. Budden wrote:
> Forwarding to vim-dev as requested by Bram... any cscope/vim experts here?
>
> Al
>
> -- Forwarded message --
> From: Bram Moolenaar
> Date: 22 May 2013 22:02
> Subje
On Sun, May 26, 2013 at 9:21 PM, ZyX wrote:
> Make vim.Dictionary look more like built-in dict:
>
> - Add .{keys,values,items,get,pop,has_key,popitem}
>
popitem(key) returns empty key.
:py x = vim.Dictionary()
:py x['y'] = 'z'
:py print x.popitem('y')
('', 'z')
And perhaps popitem(key) should
On Jun 1, 2013, at 5:07 PM, Marc Weber wrote:
> I've been thinking about what's causing trouble to me.
> Lack of workflows - lack of documentation.
>
> http://vim.sourceforge.net/ -> download -> patch
> No hint about how patches should be submitted.
> No hinting about release cycles
> NO hintin
You are right, thanks. Should have reread the docs.
--
--
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 subscr
# HG changeset patch
# User ZyX
# Date 1370141913 -14400
# Branch python-extended-4
# Node ID aeb6697bc6851e894681f9baad6ea9dc808c6714
# Parent 7698aef182526761915fa4c3fa02080555a1b327
Change the meaning of popitem: it should not accept any arguments
diff -r 7698aef18252 -r aeb6697bc685 runtime/
ZyX told me that I should try to write the way the source code looks.
Now I find that files mix tab with spaces etc.
The src/README.txt talks about many things, but not about how to
configure Vim to write Vim's .c code.
Would you mind adding a section or a reference to a .vim file describing
how
On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote:
> ZyX told me that I should try to write the way the source code looks.
>
>
>
> Now I find that files mix tab with spaces etc.
>
>
>
> The src/README.txt talks about many things, but not about how to
>
> configure Vim to write Vim's
On Sat, Jun 01, 2013 at 10:49:37PM -0700, Ben Fritz wrote:
> On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote:
> > ZyX told me that I should try to write the way the source code looks.
> >
> > Now I find that files mix tab with spaces etc.
> >
> > The src/README.txt talks about many thi
Hi
Attached patch fixes a few typos in runtime/doc/{pattern,if_pyth}.txt.
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 re
The simple test case (bottom) is interruptable, while catching sigint using a
signal handler
This patch tries to catch all common cases by replacing
got_int = TRUE with my own function. I didn't catch all, only those who seemed
related to ctrl-c (by comments):
http://mawercer.de/tmp/attempt-python
Hi,
On Sat, Jun 1, 2013 at 10:58 PM, tooth pik wrote:
> On Sat, Jun 01, 2013 at 10:49:37PM -0700, Ben Fritz wrote:
>> On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote:
>> > ZyX told me that I should try to write the way the source code looks.
>> >
>> > Now I find that files mix tab with
46 matches
Mail list logo
