Vim 7.4a ready for beta testing

Showing 1-36 of 36 messages
Vim 7.4a ready for beta testing Bram Moolenaar 7/6/13 6:59 AM

Hello Vim users,


Announcing:  Vim (Vi IMproved) version 7.4a BETA


This is the first BETA release of Vim 7.4.

Please check that the distribution is OK.  I haven't done one for a long
time.  Report anything that isn't right.  That includes a crash but also
a typo in the documentation or a missing file.


The biggest additions since 7.3:
- A new, faster regular expression engine.
- More than a thousand fixes and small improvements.

Once you have installed Vim 7.4a BETA you can find details about the
changes since Vim 7.3 with:
        :help version-7.4


Gratitude
---------

If you like Vim, please consider helping poor children in the south of
Uganda: http://iccf-holland.org


Where to get it
---------------

The best way to obtain the latest Vim 7.4 is using Mercurial.
Summary:
        hg clone https://vim.googlecode.com/hg/ vim
        cd vim
        hg update
More information here: http://www.vim.org/mercurial.php
The tag for this beta version is v7-4a.

For MS-Windows most of you will want the self-installing executable:
        ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74a.exe

Information about which files to download for what system (don't use the
links, they are still for Vim 7.3):
        http://www.vim.org/download.php

A list of mirror sites can be found here:
        http://www.vim.org/mirrors.php


The files available for download:

UNIX:
sources + runtime files, bzip2 compressed:
        ftp://ftp.vim.org/pub/vim/unstable/unix/vim-7.4a.tar.bz2

VARIOUS:
help files converted to HTML:
        ftp://ftp.vim.org/pub/vim/unstable/doc/vim74ahtml.zip

MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
        ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74a.exe

MS-WINDOWS separate files:
Runtime files:
        ftp://ftp.vim.org/pub/vim/unstable/pc/vim74art.zip
GUI binary for Windows 95/98/NT/2000/XP/7:
        ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74a.zip
GUI binary with OLE support:
        ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74aole.zip
Console version for Windows NT/2000/XP/7:
        ftp://ftp.vim.org/pub/vim/unstable/pc/vim74aw32.zip
Sources for PC (with CR-LF):
        ftp://ftp.vim.org/pub/vim/unstable/pc/vim74asrc.zip

For debugging:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74a.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74aole.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74aw32.pdb


Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The 32-bit console version for MS-DOS/Windows 95/98
- The 16 bit MS-Windows version


Mailing lists
-------------

For user questions you can turn to the Vim mailing list.  There are a
lot of tips, scripts and solutions.  You can ask your Vim questions, but
only if you subscribe.  See http://www.vim.org/maillist.php#vim

If you want to help Vim development, discuss new features or get the
latest patches, subscribe to the vim-dev mailing list.  See
http://www.vim.org/maillist.php#vim-dev

Subject specific lists:
Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte
Macintosh issues:  http://www.vim.org/maillist.php#vim-mac

Before you ask a question you should search the archives, someone may
already have given the answer.


Reporting bugs
--------------

Send them to <vim...@vim.org>.  Please describe the problem precisely.
All the time spent on answering mail is subtracted from the time that is
spent on improving Vim!  Always give a reproducible example and try to
find out which settings or other things influence the appearance of the
bug.  Try starting without your own vimrc file: "vim -u NONE".  Try
different machines if possible.  See ":help bugs" in Vim.  Send a patch
if you can!


Happy Vimming!


--
Q: What kind of stuff do you do?
A: I collect hobbies.

 /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///
Re: Vim 7.4a ready for beta testing glts 7/6/13 10:20 AM
On Sat, Jul 6, 2013 at 3:59 PM, Bram Moolenaar <Br...@moolenaar.net> wrote:
> Announcing:  Vim (Vi IMproved) version 7.4a BETA
>
>
> This is the first BETA release of Vim 7.4.
>
> Please check that the distribution is OK.  I haven't done one for a long
> time.  Report anything that isn't right.  That includes a crash but also
> a typo in the documentation or a missing file.

I can't find the bug I reported earlier in the todo list.
https://groups.google.com/d/msg/vim_dev/o5VRJl9ZbsA/-o-JQRHcvhcJ

It continues to be a problem in a plugin of mine that attempts to
display a two-line message on VimEnter. Please add it to todo.txt.
Thanks.


--
David Bürgin
Re: Vim 7.4a ready for beta testing glts 7/6/13 11:39 AM
On Sat, Jul 6, 2013 at 3:59 PM, Bram Moolenaar <Br...@moolenaar.net> wrote:
> Announcing:  Vim (Vi IMproved) version 7.4a BETA
>
>
> This is the first BETA release of Vim 7.4.
>
> Please check that the distribution is OK.  I haven't done one for a long
> time.  Report anything that isn't right.  That includes a crash but also
> a typo in the documentation or a missing file.

Just saw this: This line is redundant given the following one, isn't it?

diff -r 6ec6b7ff2d43 runtime/syntax/help.vim
--- a/runtime/syntax/help.vim    Sat Jul 06 15:44:11 2013 +0200
+++ b/runtime/syntax/help.vim    Sat Jul 06 20:31:57 2013 +0200
@@ -58,7 +58,6 @@
 syn match helpSpecial        "N  N"he=s+1
 syn match helpSpecial        "Nth"me=e-2
 syn match helpSpecial        "N-1"me=e-2
-syn match helpSpecial        "{[-a-zA-Z0-9'":%#=[\]<>.,]\+}"
 syn match helpSpecial        "{[-a-zA-Z0-9'"*+/:%#=[\]<>.,]\+}"
 syn match helpSpecial        "\s\[[-a-z^A-Z0-9_]\{2,}]"ms=s+1
 syn match helpSpecial        "<[-a-zA-Z0-9_]\+>"
Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/6/13 12:36 PM

glts wrote:

> Just saw this: This line is redundant given the following one, isn't it?
>
> diff -r 6ec6b7ff2d43 runtime/syntax/help.vim
> --- a/runtime/syntax/help.vim    Sat Jul 06 15:44:11 2013 +0200
> +++ b/runtime/syntax/help.vim    Sat Jul 06 20:31:57 2013 +0200
> @@ -58,7 +58,6 @@
>  syn match helpSpecial        "N  N"he=s+1
>  syn match helpSpecial        "Nth"me=e-2
>  syn match helpSpecial        "N-1"me=e-2
> -syn match helpSpecial        "{[-a-zA-Z0-9'":%#=[\]<>.,]\+}"
>  syn match helpSpecial        "{[-a-zA-Z0-9'"*+/:%#=[\]<>.,]\+}"
>  syn match helpSpecial        "\s\[[-a-z^A-Z0-9_]\{2,}]"ms=s+1
>  syn match helpSpecial        "<[-a-zA-Z0-9_]\+>"

Yes, looks like it.

--
You can be stopped by the police for biking over 65 miles per hour.
You are not allowed to walk across a street on your hands.
                [real standing laws in Connecticut, United States of America]
Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/6/13 12:36 PM
Autocommands should not have side effects.  And if they do you'll have
to see if that works.

Especially autocommands that are triggered on mode changes will also
update the mode message, and thus clear the command line.  Changing that
will most likely cause trouble for others.

--
It is illegal for anyone to try and stop a child from playfully jumping over
puddles of water.
                [real standing law in California, United States of America]
Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/7/13 5:51 PM
Bram Moolenaar wrote:

> Announcing:  Vim (Vi IMproved) version 7.4a BETA
>
> This is the first BETA release of Vim 7.4.
>
> Please check that the distribution is OK.  I haven't done one for a long
> time.  Report anything that isn't right.  That includes a crash but also
> a typo in the documentation or a missing file.

mid-2010 macbookpro
macosx-10.6.8
gcc-4.2.1

obtained vim-7.4a.002 via hg (same result via ftp).

configure \
    --disable-darwin \
    --with-x \
    --enable-gui=motif \
    --enable-multibyte \
    --with-mac-arch=current \
    --with-features=huge \
    --disable-acl

Test results:
test96 FAILED
TEST FAILURE

diff -u test96.ok test96.failed
--- test96.ok   2013-07-08 10:12:36.000000000 +1000
+++ test96.failed       2013-07-08 10:15:31.000000000 +1000
@@ -4,6 +4,8 @@
   - quickfix claims that the file name displayed is: test://bar.txt
 Test B:
   - number of window open: 2
+Test B:
+  - number of window open: 2
 Test C:
   - 'buftype' of the location list window: quickfix
   - buffer displayed in the 2nd window: test://quux.txt

i.e. the "Test B" section of the file is repeated.

cheers,
raf

p.s. ftp.vim.org:pub/vim/unstable/patxhes/7.4a/MD5 doesn't contain
an md5 sum for 7.4a.002 (but MD5SUMS does).

Re: Vim 7.4a ready for beta testing glts 7/8/13 9:06 AM
On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote:
> Announcing:  Vim (Vi IMproved) version 7.4a BETA
>
>
> This is the first BETA release of Vim 7.4.
>
> Please check that the distribution is OK.  I haven't done one for a long
> time.  Report anything that isn't right.  That includes a crash but also
> a typo in the documentation or a missing file.

What was the last word on test86?

It fails for me on Ubuntu 12.04 with 7.4a and --enable-pythoninterp. But
that is expected, or is it not? And there is no workaround to make it
green for the release?
Re: Vim 7.4a ready for beta testing ZyX 7/8/13 10:11 AM

For me it seems to be an Ubuntu bug. I have suggested two workarounds in the relevant thread, but that message was not replied to regarding what should actually be done.

> --
> --
> 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/8/13 11:59 AM

Nikolay Pavlov wrote:

> On Jul 8, 2013 8:06 PM, "glts" <676c...@gmail.com> wrote:
> >
> > On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote:
> > > Announcing:  Vim (Vi IMproved) version 7.4a BETA
> > >
> > >
> > > This is the first BETA release of Vim 7.4.
> > >
> > > Please check that the distribution is OK.  I haven't done one for a long
> > > time.  Report anything that isn't right.  That includes a crash but also
> > > a typo in the documentation or a missing file.
> >
> > What was the last word on test86?
> >
> > It fails for me on Ubuntu 12.04 with 7.4a and --enable-pythoninterp. But
> > that is expected, or is it not? And there is no workaround to make it
> > green for the release?
>
> For me it seems to be an Ubuntu bug. I have suggested two workarounds in
> the relevant thread, but that message was not replied to regarding what
> should actually be done.

It's related to using the static library.  Since many Linux users will
have this problem it would be better to fix it in Vim, we can't expect
everybody to fix their Python package.

It's really a problem with the test, since it passes fine with the
dynamic library.  It's not that the Python interface is broken.

--
My Go, this amn keyboar oesn't have a .
Re: Vim 7.4a ready for beta testing ZyX 7/8/13 12:26 PM


On Jul 8, 2013 10:59 PM, "Bram Moolenaar" <Br...@moolenaar.net> wrote:
>
>
> Nikolay Pavlov wrote:
>
> > On Jul 8, 2013 8:06 PM, "glts" <676c...@gmail.com> wrote:
> > >
> > > On Saturday, July 6, 2013 3:59:06 PM UTC+2, Bram Moolenaar wrote:
> > > > Announcing:  Vim (Vi IMproved) version 7.4a BETA
> > > >
> > > >
> > > > This is the first BETA release of Vim 7.4.
> > > >
> > > > Please check that the distribution is OK.  I haven't done one for a long
> > > > time.  Report anything that isn't right.  That includes a crash but also
> > > > a typo in the documentation or a missing file.
> > >
> > > What was the last word on test86?
> > >
> > > It fails for me on Ubuntu 12.04 with 7.4a and --enable-pythoninterp. But
> > > that is expected, or is it not? And there is no workaround to make it
> > > green for the release?
> >
> > For me it seems to be an Ubuntu bug. I have suggested two workarounds in
> > the relevant thread, but that message was not replied to regarding what
> > should actually be done.
>
> It's related to using the static library.  Since many Linux users will
> have this problem it would be better to fix it in Vim, we can't expect
> everybody to fix their Python package.

I have suggested a number of solutions. I would prefer failing to build with semi-static python if problem is detected. I.e. it would mean that maintainers of vim packages in distributions having this problem will be forced to decide whether they will fix python library or build with dynamic linking. Other solution is a badly looking hack.

And it is *not* related to *only* using static library. There must be specific linking flag passed for the problem to be seen. It should also affect any program that embeds python interpreter and uses PyIter_Check (and maybe some other macros I am not aware about that uses pointer to some function). Apparently there are not many: normally for this kind of things EAFP* principle is used meaning that one first tries using object as an iterator and if this fails switches to some alternative.

* Easier to Ask for Forgiveness then for Permission: like below

    #EAFP
    try:
        run(d[key])
    except KeyError:
        handle_missing_key()

    #non-EAFP
    if key in d:
        run(d[key])
    else:
        handle_missing_key()

> It's really a problem with the test, since it passes fine with the
> dynamic library.  It's not that the Python interface is broken.

No, it is not a problem with a test. As PyIter_Check always succeeds it disables all subsequent checks (AFAIR for numbers using number protocol). This means there will be bugs under certain condition. I can move these checks up in order to make problem less severe (this will make python throw exception from the different location and execute some unnecessary code, that's all).

Re: Vim 7.4a ready for beta testing (test96 FAILED) Bram Moolenaar 7/9/13 6:33 AM
That's strange.  Please check that your version of src/testdir/test96.in
is the same as
https://code.google.com/p/vim/source/browse/src/testdir/test96.in

> p.s. ftp.vim.org:pub/vim/unstable/patxhes/7.4a/MD5 doesn't contain
> an md5 sum for 7.4a.002 (but MD5SUMS does).

Fixed that.  The script had wrong dependencies (always was that way but
someone only became a problem this time).

--
Why is "abbreviation" such a long word?
Re: Vim 7.4a ready for beta testing Yukihiro Nakadaira 7/9/13 7:22 AM

Easy workaround is using -fPIC or -fPIE.

$ CFLAGS=-fPIE ./configure --enable-pythoninterp=yes && make test

--
Yukihiro Nakadaira - yukihiro....@gmail.com
Re: Vim 7.4a ready for beta testing glts 7/9/13 12:22 PM
Indeed. I don't understand the consequences but this makes the test
pass. Thanks.
Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/9/13 7:06 PM
it's the same.

MD5 (/usr/local/src/vim74/src/testdir/test96.in) = 3222973df5598f7ff3297d3cf9b5ecd9

i've tried with three separate copies of 7.4a.010:

 hg (https://vim.googlecode.com/hg/) test96 fails
 hg (https://code.google.com/p/vim)  test96 fails
 ftp (ftp.vim.org)                   test96 passes

how wierd is that?

the two hg versions are the same but there are some differences
between them and the ftp version. the differences are that the
ftp version has older versions of:

  Makefile
  runtime/compiler/checkstyle.vim
  runtime/compiler/javac.vim
  runtime/compiler/php.vim
  runtime/compiler/se.vim
  runtime/compiler/tcl.vim
  runtime/compiler/tidy.vim
  runtime/compiler/xmllint.vim
  runtime/doc/diff.txt
  runtime/doc/options.txt
  runtime/doc/todo.txt
  runtime/doc/uganda.txt
  runtime/doc/version7.txt
  runtime/plugin/tohtml.vim
  runtime/synmenu.vim
  runtime/syntax/2html.vim
  runtime/syntax/help.vim
  src/po/nl.po
  src/po/pl.UTF-8.po
  src/po/pl.cp1250.po
  src/po/pl.po
  src/po/ru.cp1251.po
  src/po/ru.po

i don't know if that helps. the actual diff can be found at
http://raf.org/tmp/vim74a.010-ftp-v-code.google.com-p-vim.diff
if it's of any use.

it's odd that yesterday the ftp version of 7.4a.002 failed but
today the ftp version of 7.4a.010 passed. i just tested the ftp
version again at every patchlevel up to 010 and they all worked.
the hg version still fails though. bizarre.

cheers,
raf

Re: Vim 7.4a ready for beta testing Milan Vancura 7/10/13 2:06 AM
Hello.

> The biggest additions since 7.3:
> - A new, faster regular expression engine.
> - More than a thousand fixes and small improvements.

...and all the work about python? What's the current status, why it is not
listed? It was a set of dozens and dozens patches and I'm lost now what's the
result status.

Thanks,

Milan Vancura
Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/10/13 3:25 AM
Well, that's the problem, how to summarize that?

--
The chat program is in public domain.  This is not the GNU public license.
If it breaks then you get to keep both pieces.
                -- Copyright notice for the chat program
Re: Vim 7.4a ready for beta testing (test96 FAILED) Bram Moolenaar 7/10/13 3:25 AM
If you can't reproduce a problem you had earlier, it's likely that
something else matters.  Can you run the test under valgrind?  There is
a line in src/testdir/Makefile you can uncomment.

The test is about location lists, the runtime files should not matter.
If they do, it might be that things shift around in memory and trigger
the problem somehow.

--
God made machine language; all the rest is the work of man.
Re: Vim 7.4a ready for beta testing Lech Lorens 7/10/13 4:12 AM
On 10 July 2013 12:25, Bram Moolenaar <Br...@moolenaar.net> wrote:
>
> Milan Vancura wrote:
>
>> > The biggest additions since 7.3:
>> > - A new, faster regular expression engine.
>> > - More than a thousand fixes and small improvements.
>>
>> ...and all the work about python? What's the current status, why it is not
>> listed? It was a set of dozens and dozens patches and I'm lost now what's the
>> result status.
>
> Well, that's the problem, how to summarize that?

How about "A more pythonic Python interface"?

Cheers,
Lech
Re: Vim 7.4a ready for beta testing Milan Vancura 7/10/13 5:08 AM
> How about "A more pythonic Python interface"?

I would prefer clearer summary: what exactly is now possible?

Example questions:

* Can I write a script for vim in python only, without vimscript?

* What's the advantage? Is there new data model easier to understand than
  a myriad of random vimscript functions? Object model?

* Are there any bonus functions available from python only? For example
  a possibility to use something like CursorDown() instead of remapping of keys
  which are only hoped to do such action (and could be already remapped by
  another plugin)?

* (plugins like) modules usable in another plugins so a system of plugin
  libraries becomes possible?

etc. etc.

I really do not know what's the status now. It may be that my questions are too
much sci-fi :-)

Milan
Re: Vim 7.4a ready for beta testing Milan Vancura 7/10/13 5:11 AM
ZyX,

it's probably beter to ask you directly... Can you send a short description,
please?

Milan
Re: Vim 7.4a ready for beta testing Tony Mechelynck 7/10/13 6:51 AM
On 10/07/13 14:08, Milan Vancura wrote:
>> How about "A more pythonic Python interface"?
>
> I would prefer clearer summary: what exactly is now possible?
>
> Example questions:
>
> * Can I write a script for vim in python only, without vimscript?

Yes, but it will only run in a Vim compiled with +python, or in a Vim
compiled with +python/dyn if Vim can find the Python shared libraries at
runtime. (pr +python3 +python3/dyn for Python 3).

>
> * What's the advantage? Is there new data model easier to understand than
>    a myriad of random vimscript functions? Object model?

The advantage of Vimscript is that all versions of Vim understand it,
and you can use ":if has(…)" and ":if exists(…)" to check if the version
you're currently running it has the features you need.

The advantage of Python is that if you already used Python before
starting to use Vim you don't need to learn one more programming language.

>
> * Are there any bonus functions available from python only? For example
>    a possibility to use something like CursorDown() instead of remapping of keys
>    which are only hoped to do such action (and could be already remapped by
>    another plugin)?

Any Python function not related to Vim (and not defined by the Vim
module) becomes available if your Vim is compiled with +python (or with
+python/dyn and it knows where to find the Python libraries) (similarly
mutatis mutandis for Python 3). You will of course need to import the
relevant module(s), and call the appropriate Python function(s), either
individually by :python, repeatedly by :pydo, or collectively by
invoking either an external Python script by :pyfile, or a Python
here-script by :python << EOF (or, in all cases, the corresponding
Vim-Python 3 interfacing commands).

Otherwise, AFAIK the "Vim" module importable into Python just makes the
following kinds of functions available to Python:
(a) commands which Vimscript can handle natively
(b) functions related to interfacing between Vim and Python, including
representing Vim buffers etc. as python objects.

>
> * (plugins like) modules usable in another plugins so a system of plugin
>    libraries becomes possible?

see above

>
> etc. etc.
>
> I really do not know what's the status now. It may be that my questions are too
> much sci-fi :-)
>
> Milan
>

I think they are quite reasonable, even if I don't have all the answers.


Best regards,
Tony.
--
Put your Nose to the Grindstone!
                -- Amalgamated Plastic Surgeons and Toolmakers, Ltd.

Re: Vim 7.4a ready for beta testing ZyX 7/10/13 8:09 AM


On Jul 10, 2013 5:51 PM, "Tony Mechelynck" <antoine.m...@gmail.com> wrote:
>
> On 10/07/13 14:08, Milan Vancura wrote:
>>>
>>> How about "A more pythonic Python interface"?
>>
>>
>> I would prefer clearer summary: what exactly is now possible?
>>
>> Example questions:
>>
>> * Can I write a script for vim in python only, without vimscript?
>
>
> Yes, but it will only run in a Vim compiled with +python, or in a Vim compiled with +python/dyn if Vim can find the Python shared libraries at runtime. (pr +python3 +python3/dyn for Python 3).

No, you can't live without vim.*eval or vim.command even if you don't care about old versions.

> --
> --
> 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 unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/10/13 7:45 PM
the hg version still produced the error just now.
i uncommented the VALGRIND definition in src/tesdir/Makefile
and uncommented the LEAK_CFLAGS = -DEXITFREE line in src/Makefile
and recompiled vim and reran the tests and test96 passed this time.
here's the valgrind report for test96:

==8976== Memcheck, a memory error detector
==8976== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==8976== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==8976== Command: ../vim -u unix.vim -U NONE --noplugin -s dotest.in test96.in
==8976== Parent PID: 3970
==8976==
--8976-- ../vim:
--8976-- dSYM directory is missing; consider using --dsymutil=yes
==8976== Warning: ignored attempt to set SIGUSR2 handler in sigaction();
==8976==          the SIGUSR2 signal is used internally by Valgrind
==8976==
==8976== HEAP SUMMARY:
==8976==     in use at exit: 1,062,359 bytes in 2,090 blocks
==8976==   total heap usage: 24,453 allocs, 22,363 frees, 13,406,283 bytes allocated
==8976==
==8976== 40 (16 direct, 24 indirect) bytes in 1 blocks are definitely lost in loss record 324 of 753
==8976==    at 0x1002D848B: calloc (vg_replace_malloc.c:597)
==8976==    by 0x10065ABE1: XtCalloc (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x10040A216: _XmPushWidgetExtData (in /opt/local/lib/libXm.4.dylib)
==8976==    by 0x100419CE5: SecondaryObjectCreate (in /opt/local/lib/libXm.4.dylib)
==8976==    by 0x100417C5A: InitializePrehook (in /opt/local/lib/libXm.4.dylib)
==8976==    by 0x10040923E: InitializeRootWrapper (in /opt/local/lib/libXm.4.dylib)
==8976==    by 0x100662F62: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==    by 0x100662F2D: CallInitialize (in /opt/local/lib/libXt.6.dylib)
==8976==
==8976== LEAK SUMMARY:
==8976==    definitely lost: 16 bytes in 1 blocks
==8976==    indirectly lost: 24 bytes in 1 blocks
==8976==      possibly lost: 0 bytes in 0 blocks
==8976==    still reachable: 1,060,886 bytes in 2,083 blocks
==8976==         suppressed: 1,433 bytes in 5 blocks
==8976== Reachable blocks (those to which a pointer was found) are not shown.
==8976== To see them, rerun with: --leak-check=full --show-reachable=yes
==8976==
==8976== For counts of detected and suppressed errors, rerun with: -v
==8976== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)

Re: Vim 7.4a ready for beta testing (test96 FAILED) Bram Moolenaar 7/11/13 2:30 PM
What compiler are you using?  This looks like OSX.  But I thought there
was no valgrind for that.

Runnint with valgrind also shifts things around.  Although you would be
really lucky if the wrong accesses happen to fall in valid memory areas.

--
How come wrong numbers are never busy?
Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/11/13 11:37 PM
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
Copyright (C) 2007 Free Software Foundation, Inc.

> This looks like OSX.  But I thought there
> was no valgrind for that.

it's macosx-10.6.8.
the valgrind is from macports.
the gcc is from XCode-3.2.6.

> Running with valgrind also shifts things around.  Although you would be
Re: Vim 7.4a ready for beta testing Rob Owens 7/12/13 7:37 AM
I downloaded and ran ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74a.exe

All of the syntax files I provided (for Innovation Data Processing) are there, but they are not included in synmenu.vim.  However when I pull from Mercurial, synmenu.vim includes the Innovation Data Processing entries.

You may have expected this, based on the build dates, but I wanted to bring it to your attention just in case.

-Rob

Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/12/13 11:55 AM
Yeah, I discovered the syntax menu wasn't updated after building the
Windows binary.  I decided not to start all over.

I'll do another beta release, perhaps in a week.  So far things look
good, thus that may be the last one.

--
SOLDIER: What?  Ridden on a horse?
ARTHUR:  Yes!
SOLDIER: You're using coconuts!
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///
Re: Vim 7.4a ready for beta testing (test96 FAILED) Bram Moolenaar 7/12/13 11:55 AM

Raf wrote:

[...]

> > > the hg version still produced the error just now.
> > > i uncommented the VALGRIND definition in src/tesdir/Makefile
> > > and uncommented the LEAK_CFLAGS = -DEXITFREE line in src/Makefile
> > > and recompiled vim and reran the tests and test96 passed this time.
> > > here's the valgrind report for test96:
> > >
> > > ==8976== Memcheck, a memory error detector
> > > ==8976== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> > > ==8976== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
> > > ==8976== Command: ../vim -u unix.vim -U NONE --noplugin -s dotest.in test96.in
> > > ==8976== Parent PID: 3970
> > > ==8976==
> > > --8976-- ../vim:
> > > --8976-- dSYM directory is missing; consider using --dsymutil=yes
> > > ==8976== Warning: ignored attempt to set SIGUSR2 handler in sigaction();
> > > ==8976==          the SIGUSR2 signal is used internally by Valgrind
> >
> > What compiler are you using?
>
> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> > This looks like OSX.  But I thought there
> > was no valgrind for that.
>
> it's macosx-10.6.8.
> the valgrind is from macports.
> the gcc is from XCode-3.2.6.
>
> > Running with valgrind also shifts things around.  Although you would be
> > really lucky if the wrong accesses happen to fall in valid memory areas.

Have you tried building without the optimizer?  The gcc optimizer can be
a bit aggressive.

--
SOLDIER: Where did you get the coconuts?
ARTHUR:  Through ... We found them.
SOLDIER: Found them?  In Mercea.  The coconut's tropical!
Re: Vim 7.4a ready for beta testing ZyX 7/13/13 10:21 AM
diff -r 1205c07d8df2 runtime/doc/version7.txt
--- a/runtime/doc/version7.txt        Сб. июля 13 16:57:24 2013 +0400
+++ b/runtime/doc/version7.txt        Сб. июля 13 21:20:00 2013 +0400
@@ -70,6 +70,7 @@ Fixed                                        |fixed-7.3|
 
 VERSION 7.4                        |version-7.4|
 New regexp engine                        |new-regexp-engine|
+Better vim ↔ python interface                |new-python-interfac|
 Changed                                        |changed-7.4|
 Added                                        |added-7.4|
 Fixed                                        |fixed-7.4|
@@ -10182,16 +10183,168 @@ is now working fine.  Previously Vim cou
 
 More information here: |two-engines|
 
+Better vim ↔ python interface                        *new-python-interface*
+-----------------------------
+
+Added |python-bindeval| function. Unlike |python-eval| this one returns
+  |python-Dictionary|, |python-List| and |python-Function| objects for
+  dictionaries lists and functions respectively in place of their python
+  built-in equivalents (or None if we are talking about function references).
+For simple types this function returns python built-in types and not only
+  python `str()` like |python-eval| does. On python 3 it will return `bytes()`
+  objects in place of `str()` ones avoiding possibility of UnicodeDecodeError.
+Interface of new objects mimics standard python `dict()` and `list()`
+  interfaces to some extent. Extent will be improved in the future.
+
+Added special |python-vars| objects also available for |python-buffer| and
+|python-window|. They ease access to VimL variables from python.
+
+Now you no longer need to alter `sys.path` to import your module: special
+hooks are responsible for importing from {rtp}/python2, {rtp}/python3 and
+{rtp}/pythonx directories (for python 2, python 3 and both respectively).
+See |python-special-path|.
+
+Added possibility to work with |tabpage|s through |python-tabpage| object.
+
+Added automatic conversion of vim errors and exceptions to python
+exceptions.
+
+Changed the behavior of |python-buffers| object: it now uses buffer numbers
+as keys in place of the index of the buffer in the internal buffer list.
+This should not break anything as the only way to get this index was
+iterating over |python-buffers|.
+
+Added |:pydo| and |:py3do| commands.
+
+Added |pyeval()| and |py3eval()| functions.
+
+Now in all places which previously accepted `str()` objects in both python
+version both `str()` and `unicode()` (python 2) or `bytes()` and `str()`
+(python 3) are accepted.
+
+|python-window| has gained `.col` and `.row` attributes that are currently
+the only way to get internal window positions.
+
+Added or fixed support for `dir()` in vim python objects.
+
+Old python versions (≤2.2) are no longer supported. Building with them did
+not work anyway.
 
 Changed                                                        *changed-7.4*
 -------
 
-Todo.
-
+Functions:
+        Added ability to use |Dictionary-function|s for |sort()|ing, via
+        optional third argument. (Nikolay Pavlov)
+
+        Added special |expand()| argument that expands to the current line
+        number.
+
+        Made it possible to force |char2nr()| always give unicode codepoints
+        regardless of current encoding. (Yasuhiro Matsumoto)
+
+        Made it possible for functions generating file list generate |List|
+        and not NL-separated string. (e.g. |glob()|, |expand()|) (Christian
+        Brabandt)
+
+        Functions that obtain variables from the specific window, tabpage or
+        buffer scope dictionary can now return specified default value in
+        place of empty string in case variable is not found. (|gettabvar()|,
+        |getwinvar()|, |getbufvar()|) (Shougo Matsushita, Hirohito Higashi)
+
+Options:
+        Added ability to automatically save selection into the system
+        clipboard when using non-GUI version of vim (autoselectplus in
+        'clipboard'). Also added ability to use system clipboard as default
+        register (previously only primary selection could be used). (Ivan
+        Krasilnikov, Christian Brabandt, Bram Moolenaar)
+
+        Added special 'shiftwidth' value that makes 'sw' follow 'tabstop'. As
+        indenting via 'indentexpr' became tricky |shiftwidth()| function was
+        added. Also added equivalent special value to 'softtabstop' option.
+        (Christian Brabandt, so8res)
+
+        Added ability to delete comment leader when using |J| by `j` flag in
+        'formatoptions' (|fo-table|). (Lech Lorens)
+
+        Added ability to control indentation inside namespaces: |cino-N|.
+        (Konstantin Lepa)
+
+        Added ability to control alignment inside `if` condition separately
+        from alignment inside function arguments: |cino-k|. (Lech Lorens)
+
+        Added ability to show absolute number in number column when
+        'relativenumber' option is on. (Christian Brabandt)
+
+Comands:
+        Made it possible to remove all signs from the current buffer using
+        |:sign-unplace|. (Christian Brabandt)
+
+        Added |:language| autocompletion. (Dominique Pelle)
+
+        |:diffoff| now saves the local values of some settings and restores
+        them in place of blindly resetting them to the defaults. (Christian
+        Brabandt)
+
+        Added |:map-nowait| creating mapping which when having lhs that is the
+        prefix of another mapping’s lhs will not allow vim to wait for user to
+        type more characters to resolve ambiguity, forcing vim to take the
+        shorter alternative: one with <nowait>.
+
+        Added more |:command-complete| completion types: |:behave| suboptions,
+        color schemes, compilers, |:cscope| suboptions, files from 'path',
+        |:history| suboptions, locale names, |:syntime| suboptions, user
+        names. (Dominique Pelle)
+
+Other:
+        Improved support for cmd.exe. (Ben Fritz, Bram Moolenaar)
+
+        Added |v:windowid| variable containing current window number in GUI
+        vim. (Christian J. Robinson, Lech Lorens)
+
+        Lua interface now also uses userdata binded to vim structures. (Taro
+        Muraoka, Luis Carvalho)
+
+        Added rxvt-unicode and >xterm-277 mouse support. (Yiding Jia, Hayaki
+        Saito)
 
 Added                                                        *added-7.4*
 -----
 
+Added support for |Lists| and |Dictionaries| in |viminfo|. (Christian
+Brabandt)
+
+Functions:
+        Bitwise functions: |and()|, |or()|, |invert()|, |xor()|.
+
+        Added |luaeval()| function. (Taro Muraoka, Luis Carvalho)
+
+        Added |sha256()| function. (Tyru, Hirohito Higashi)
+
+        Added |wildmenumode()| function. (Christian Brabandt)
+
+        Debugging functions: |screenattr()|, |screenchar()|, |screencol()|,
+        |screenrow()|. (Simon Ruderich, Bram Moolenaar)
+
+Autocommands:
+        Added |InsertCharPre| event launched before inserting character.
+        (Jakson A. Aquino)
+
+        Added |CompleteDone| event launched after finishing completion in
+        insert mode. (idea by Florian Klein)
+
+        Added |QuitPre| event launched when commands that can either close vim
+        or only some window(s) are launched.
+
+        Added |TextChanged| and |TextChangedI| events launched when text is
+        changed.
+
+Commands:
+        |:syntime| command useful for debugging.
+
+Options:
+        Made it possible to ignore case when completing: 'wildignorecase'.
+
 Various syntax, indent and other plugins were added.
 
 
Re: Vim 7.4a ready for beta testing Bram Moolenaar 7/13/13 11:58 AM

ZyX wrote:

> diff -r 1205c07d8df2 runtime/doc/version7.txt
> --- a/runtime/doc/version7.txt        Сб. июля 13 16:57:24 2013 +0400
> +++ b/runtime/doc/version7.txt        Сб. июля 13 21:20:00 2013 +0400
> @@ -70,6 +70,7 @@ Fixed                                        |fixed-7.3|
>  
>  VERSION 7.4                        |version-7.4|
>  New regexp engine                        |new-regexp-engine|
> +Better vim ↔ python interface                |new-python-interfac|
>  Changed                                        |changed-7.4|
>  Added                                        |added-7.4|
>  Fixed                                        |fixed-7.4|
> @@ -10182,16 +10183,168 @@ is now working fine.  Previously Vim cou
[...]

Thanks.  I'll include it and then make edits.  There are too many items
under "Changed".  This section is more for changes that are not fully
backwards compatible.  All new functionality should be under "Added",
even though it extends the functionality of an existing command or
function.

--
"Lisp has all the visual appeal of oatmeal with nail clippings thrown in."
                                                         -- Larry Wall
Re: Vim 7.4a ready for beta testing (test96 FAILED) Nicolas Goles Domic 7/17/13 8:24 AM
On Sunday, July 7, 2013 8:51:04 PM UTC-4, raf wrote:
> Bram Moolenaar wrote:
>
>
>
> > Announcing:  Vim (Vi IMproved) version 7.4a BETA
>
> >
>
> > This is the first BETA release of Vim 7.4.
>
> >
>
> > Please check that the distribution is OK.  I haven't done one for a long
>
> > time.  Report anything that isn't right.  That includes a crash but also
>
> > a typo in the documentation or a missing file.
>
>
>
> mid-2010 macbookpro
>
> macosx-10.6.8
>
> gcc-4.2.1
>
>
>
> obtained vim-7.4a.002 via hg (same result via ftp).
>
>
>
> configure \
>
>     --disable-darwin \
>
>     --with-x \
>
>     --enable-gui=motif \
>
>     --enable-multibyte \
>
>     --with-mac-arch=current \
>
>     --with-features=huge \
>
>     --disable-acl
>
>
>
> Test results:
>
> test96 FAILED
>
> TEST FAILURE
>
>
>
> diff -u test96.ok test96.failed
>
> --- test96.ok   2013-07-08 10:12:36.000000000 +1000
>
> +++ test96.failed       2013-07-08 10:15:31.000000000 +1000
>
> @@ -4,6 +4,8 @@
>
>    - quickfix claims that the file name displayed is: test://bar.txt
>
>  Test B:
>
>    - number of window open: 2
>
> +Test B:
>
> +  - number of window open: 2
>
>  Test C:
>
>    - 'buftype' of the location list window: quickfix
>
>    - buffer displayed in the 2nd window: test://quux.txt
>
>
>
> i.e. the "Test B" section of the file is repeated.
>
>
>
> cheers,
>
> raf
>
>
>
> p.s. ftp.vim.org:pub/vim/unstable/patxhes/7.4a/MD5 doesn't contain
>
> an md5 sum for 7.4a.002 (but MD5SUMS does).

Hey Raf,

Just build fine in Mac OS X 10.8.4

gcc --version    
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

./configure output

here https://gist.github.com/Goles/89075c9254052d99b062

./vim --version

VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 17 2013 11:19:32)
MacOS X (unix) version
Included patches: 1-27
Normal version without GUI.  Features included (+) or not (-):
-arabic          +file_in_path    -mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           -mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
+builtin_terms   -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         -gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
+clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   -perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    -keymap          +postscript      +virtualedit
+comments        -langmap         +printer         +visual
-conceal         +libcall         -profile         +visualextra
+cryptv          +linebreak       -python          +viminfo
-cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             -rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
-emacs_tags      -mouseshape      -sniff           -xsmp
+eval            -mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        -mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    
-farsi           -mouse_netterm   +syntax          
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX -no-cpp-precomp  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
Linking: gcc   -L/usr/local/lib -o vim        -lm -lncurses  -liconv -framework Cocoa          

Hope this somehow helps you out a bit?
Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/21/13 6:44 PM
I compiled it with -O0 and had the same result.

cheers,
raf

Re: Vim 7.4a ready for beta testing (test96 FAILED) Yukihiro Nakadaira 7/22/13 9:45 AM
test96 failed on Windows Vista, too.

Maybe I found the cause of this problem.  test96 depends on cursor
position after switching buffer.  But it is not stable.  Try the
following script:

call setline(1, range(10))
for i in range(5)
  new
  buffer 1
  let &l:foldminlines = i
  call cursor(i, 1)
endfor
for i in range(5)
  quit
endfor
for i in range(5)
  new
  buffer 1
endfor

Now, each window have different cursor position and different
window-local option value (&l:foldminlines in this case).

I guess:
  win_free() doesn't clear buf->b_wininfo.
  After freeing memory, win_alloc() can return same address.
  Then, buf->b_wininfo is re-used for newly allocated window in spite of
  diffrent window.

--
Yukihiro Nakadaira - yukihiro....@gmail.com
Re: Vim 7.4a ready for beta testing (test96 FAILED) Bram Moolenaar 7/24/13 8:53 AM
It would be possible.  Unfortunately I could not reproduce the problem.

Please check if patch 7.4a.044 fixes the problem.

--
hundred-and-one symptoms of being an internet addict:
25. You believe nothing looks sexier than a man in boxer shorts illuminated
    only by a 17" inch svga monitor.
Re: Vim 7.4a ready for beta testing (test96 FAILED) Yukihiro Nakadaira 7/25/13 9:26 AM
The problem seems to be solved.  Thank you.

--
Yukihiro Nakadaira - yukihiro....@gmail.com
Re: Vim 7.4a ready for beta testing (test96 FAILED) raf 7/28/13 11:16 PM
it's fixed here too. thanks.

cheers,
raf

More topics »