Bram Moolenaar wrote:
The documentation is too short. Looking at it I have many questions: - Does this change the text in the buffer? I suppose not, then what happens when the text is redisplayed?
Since the data is written directly to the screen, the displayed data is lost after a redraw. No other Vim internal data is changed.
- Why only these specific functions?
This is the minimal interface that is needed so that Vim can display popup windows. It is exported to Python because the rest was much easier to implement there instead of using C. The interface is used by script#2606 to display popup windows with various lists (buffers, directory browser, recent files, etc). I find it more convenient to display lists in popup windows instead of (v)splitting every time I want to open a file or select a buffer. And since Vim doesn't provide a suitable facility I created my own.
- And why allow things that can't even be done with Vim functions?
Vim functions can't draw directly to the screen, that's true. But Vim can use ncurses through Python to achieve the same effect as provided by the exported functions. The patch is only necessary for GVim and for scripts that need to know the exact position of the cursor and the windows on the screen. In a terminal, script #2606 uses ncurses when python_screen is not present.
- The examples should be in the help. I don't see much use for it and it might break something, I'm not including this in 7.3.
No problem. It will still be included with script#2606 for those who want to use it. Thanks, Marko -- 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
