>I have included all the Python patches that I had listed in the todo
>file, except some old ones.
>
>Below is the list of remaining Python items. Please have a look and
>tell me what is still an issue and what can be dropped.
>
>There is also the patch from Yasuhiro Matsumoto that breaks the tests,
>see an earlier message about that.
>
>Also, please look at the Python interface documentation, and find
>anything that doesn't look right. We can still make a few changes
>before setting "in stone" when Vim 7.4 rolls out.
>
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>There is a ":py3do" command now, but not a ":pydo" command.
>
>Patch to print the result of a :python command. (Maxim Philippov
><[email protected]>, 2012 Aug 16) Update Aug 17.
>Patch no longer applies.
>
>Python: Adding line to buffer other than the current one doesn't work
>correctly. (Rozbujnik, 2010 Dec 19)
Found this one. It persists, script to test:
vim -u NONE -c $'let nr=bufnr("scratch", 1)\ncall setbufvar(nr, "&bt",
"nofile")\ncall setbufvar(nr, "&bh", "hide")\ncall setbufvar(nr, "&buflisted",
1)\npy import vim\ndef myprint():\n vim.buffers[2].append("hello")' -s <(<<<
$'iabc\e:py myprint()\n:w /tmp/result\n')
. If everything is fine, /tmp/result must not contain hello. Note: buffer
number
changed to 2 due to change in vim.buffers.
>Patch to dynamically load Python on Solaris. (Danek Duvall, 2009 Feb 16)
>Needs more work.
>
>":python os.chdir('/tmp')" makes short buffer names invalid. (Xavier de Gaye)
>Check directory and call shorten_fnames()?
Probably not only the python problem.
>Mac: OS/X 10.4 with Python 2.5 installed: configure finds an extra argument
>that breaks the build. (Brian Victor, 2008 Sep 1)
>
>Patch to access screen under Python. (Marko Mahni, 2010 Jul 18)
>
>Python: ":py raw_input('prompt')" doesn't work. (Manu Hack)
Persists. It not only “doesn't work”, it hangs vim.
>Win32: The Python interface only works with one version of Python, selected at
>compile time. Can this be made to work with version 2.1 and 2.2 dynamically?
>
>Python: be able to define a Python function that can be called directly from
>Vim script. Requires converting the arguments and return value.
Converting the arguments and return value can be easily done. This proposal
requires in first place not converting something, but changing the funcref
implementation (proposal mentioned in my RFC, no detailed description yet; old
detailed description written somewhere is probably outdated. AFAIR it was
expressed in the thread where it was proposed to add FFI better then libcall*).
>Python interface: add vim.message() function. (Michal Vitecek, 2002 Nov 5)
Unable to find. If equivalent to perl VIM::Msg then it is done by `print "foo"`
or `sys.stdout.write("foo\n")`.
--
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
