Loading ...
Sorry, an error occurred while loading the content.

Re: Vim 7.4a ready for beta testing

Expand Messages
  • Nikolay Pavlov
    On Jul 10, 2013 5:51 PM, Tony Mechelynck ... compiled with +python/dyn if Vim can find the Python shared libraries at runtime.
    Message 1 of 36 , Jul 10, 2013
    • 0 Attachment


      On Jul 10, 2013 5:51 PM, "Tony Mechelynck" <antoine.mechelynck@...> 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.

      >>
      >> * 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.
      >
      >
      > --
      > --
      > 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+unsubscribe@....
      > For more options, visit https://groups.google.com/groups/opt_out.
      >
      >

      --
      --
      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+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
       
       
    • raf
      ... it s fixed here too. thanks. cheers, raf -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you
      Message 36 of 36 , Jul 28, 2013
      • 0 Attachment
        Yukihiro Nakadaira wrote:

        > On Thu, Jul 25, 2013 at 12:53 AM, Bram Moolenaar <Bram@...> wrote:
        >
        > >
        > > Yukihiro Nakadaira wrote:
        > >
        > > > On Mon, Jul 8, 2013 at 9:51 AM, <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.
        > > > >
        > > >
        > > > 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.
        > >
        > > It would be possible. Unfortunately I could not reproduce the problem.
        > >
        > > Please check if patch 7.4a.044 fixes the problem.
        >
        >
        > The problem seems to be solved. Thank you.
        >
        > --
        > Yukihiro Nakadaira - yukihiro.nakadaira@...

        it's fixed here too. thanks.

        cheers,
        raf

        --
        --
        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+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      Your message has been successfully submitted and would be delivered to recipients shortly.