Re: (patch) Lua interface

2008-09-03 Thread Andy Kittner
On Wed, Sep 03, 2008 at 09:03:21AM -0400, Luis Carvalho wrote: Thanks for catching this. A new patch, that also provides a simple configure.in, is available at http://wiki.linuxfromscratch.org/blfs/attachment/wiki/vim/vim72-lua-0.2.patch.gz I have a question. The standalone Lua interpreter is

Re: [RFC] Some more python and VimL interfaces

2013-05-11 Thread Andy Kittner
On Sat, May 11, 2013 at 03:50:50PM +0200, Bram Moolenaar wrote: [...] If most things are already possible, then it should be possible to write Python functions that work as a nice interface for the functionality. Thus not change the C implementation of the Python interface. Where it is feasible t

Re: [RFC] Some more python and VimL interfaces

2013-05-12 Thread Andy Kittner
On Fri, May 10, 2013 at 03:49:45AM +0200, Bram Moolenaar wrote: ZyX wrote: This is a description of proposed new python interfaces. Well, that's a very long list. Do we really need all of this? Let's at least order by usefulness. I took some time today to look more closely at the RFC and

Re: [RFC] Some more python and VimL interfaces

2013-05-15 Thread Andy Kittner
On 05/15/13 13:06, Bram Moolenaar wrote: > > ZyX wrote: > >>> 3. vim.functions: >>> Again, the introspection is not strictly necessary, but a convenience >>> wrapper that pulls the FuncRefs will make code look much nicer. >>> In that regard I'd also offer attribute access for builtin/ glob

Re: pythonx patch - :pyx command

2013-06-01 Thread Andy Kittner
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

Re: Patch 7.3.569

2012-06-29 Thread Andy Kittner
(apologies if anyone gets this twice, the reply didn't make it to the list due to the wrong sender-adress) On 29.06.2012 15:17, Bram Moolenaar wrote:> > It appears PyCapsule_GetPointer is new in Python 2.7. We should support > Python 2.5. > > It is only used in convert_dl(). Perhaps there is an

Problem with Mingw crosscompiled vim on Win64

2010-02-02 Thread Andy Kittner
Hi All, I usually build my windows vims by cross compiling them on my linux box. This generally works like a charm, however over the years quite a few hacks and ad-hoc fixes have accumulated and I have now finally decided to get rid of them ;) One of the few things that might be interesting f

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-03 Thread Andy Kittner
On Wed, Feb 03, 2010 at 09:42:33PM +0300, Sergey Khorev wrote: Since then I have used the attached patch and just blindly returned TRUE for NCCREATE. It must have worked without I'll effects because until now I Btw the patch has a seemingly harmless side-effect: it makes client window title emp

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-03 Thread Andy Kittner
On Thu, Feb 04, 2010 at 09:11:41AM +0300, Sergey Khorev wrote: Andy, Most interesting, as DefWindowProc is still called. So I guess that indicates that _something_ goes wrong inside it. It doesn't bother to put anything but "Operation successfully completed" or something like that into GetLastE

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-04 Thread Andy Kittner
On Thu, Feb 04, 2010 at 08:15:06AM +0100, Andy Kittner wrote: It seems I found what actually is wrong. In gui_w32.c we create ASCII window class for text area, but _TextAreaWndProc forwards messages to vim_WindowProc which in turn might call wide window proc! The solution is to create wide text

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-07 Thread Andy Kittner
On Sun, Feb 07, 2010 at 09:07:38AM +1100, John Marriott wrote: [...] mingw64). However, the "File->Save As..." command no longer works. It displays " :browse confirm saveas" at the bottom of the screen but does not display the file/folder "save as" requester window. My OS is Win7 x64. MinGW i

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-07 Thread Andy Kittner
On Sun, Feb 07, 2010 at 12:46:34PM +0100, Andy Kittner wrote: According to gdb fileStruct.lStructSize ends up as 8 bytes On second reading I see that the code uses sizeof(OPENFILENAME_SIZE_VERSION_400) which is most likely not intended here, as OPENFILENAME_SIZE_VERSION_400 already contains

Re: Problem with Mingw crosscompiled vim on Win64

2010-02-07 Thread Andy Kittner
On Mon, Feb 08, 2010 at 07:57:18AM +1100, John Marriott wrote: Hi Andy, You're right. It's fixed now. Thanks very much! Regards John Your welcome! I use vim almost daily, so a little bug hunting is the least I can do to give something back. Let me take this opportunity to say a big thank you

Re: gvimext Build error on Win64 with Mingw

2010-02-13 Thread Andy Kittner
On Sun, Feb 14, 2010 at 07:23:04AM +1100, John Marriott wrote: [...] I believe that it builds ok using MS VC++ 2008. Any assistance would be greatly appreciated. Can you try the attached patch? It build fine for me with it, but I can't test if the .dll works right now ;) Regards, Andy -- Acco

Re: Planning Vim 7.3: Python3 support?

2010-05-16 Thread Andy Kittner
Hi, On Thu, Apr 29, 2010 at 03:22:51PM +0200, Roland Puntaier wrote: [..] The patch has :py3 for Python 3.x and legacy :py[thon] for Python 2.x. Python 3.x is treated as another language. Both Python 2.x and Python 3.x can be supported at the same time, if vim is configured acco

Re: Update on Vim 7.3 status

2010-05-24 Thread Andy Kittner
On Mon, May 24, 2010 at 10:56:59PM +0200, Bram Moolenaar wrote: [..] I suppose most people will want Python 2.6. I'll see if I manage to make that work. You can try it yourself, if you like. I also have a patch to support Python 3. We'll have to see if dynamically loading both will work. I

Re: Linking errors when compiled with both python and python3

2010-07-23 Thread Andy Kittner
On Fri, Jul 23, 2010 at 02:30:19PM -0400, James Vega wrote: Because we have to use RTLD_GLOBAL (since the C extensions aren't linked against libpython), it's not safe to use both the Python 2 & 3 This seems to be system dependent then. On my system the original example worked fine before the pa

Re: Linking errors when compiled with both python and python3

2010-07-24 Thread Andy Kittner
On Fri, Jul 23, 2010 at 07:17:24PM -0400, James Vega wrote: On Fri, Jul 23, 2010 at 11:05:05PM +0200, Andy Kittner wrote: Running ldd on the files in the lib-dynload directory reveals that out of my installed python versions (2.4.6, 2.5.4, 2.6.5, 2.7, 3.1.2) revealed that all c-extensions

Re: Vim 7.3: Python3 support

2010-08-09 Thread Andy Kittner
On Mon, 09 Aug 2010 12:58:20 +0200 Bram Moolenaar wrote: > > Roland Puntaier wrote: ... snip... > > > > I made the test in Vim 7.3: After removing RTLD_GLOBAL there was no crash > > any more. > > If I'm not mistaken this flag was added to make "import termios" work. > Or something like that.

Re: Neovim changes

2015-04-15 Thread Andy Kittner
On 15/04/15 14:28, Bram Moolenaar wrote: Christian Brabandt wrote: On Di, 14 Apr 2015, Bram Moolenaar wrote: It's weird to exit when running out of memory, that's not what users want. It's easy to accidentally make a Vim script that consumes all memory. It's making things easier for deve