On May 29, 2013 11:57 AM, "Marc Weber" <[email protected]> wrote:
>
> I'd like to try providing patches for the following features:
>
> - nox patch
>   https://code.google.com/r/yukihironakadaira-vim-cmdsrv-nox/
>   What is it? Allows client-server communication via sockets.
>
>   pro: only you can access your vim instances
>   con: you cannot connect to a vim instance running as root using X
>   anymore (is this bad or a feature)
>
>   Anyway, how should it look like?
>   Because there are multiple communication ways, does it makes sesne to
>   allow opting-in out eg this way?
>
>     vim --enable-client-server nox,x11
>
>   If both communication ways are allowed at the same time, which one to
>   use with --remote-* commands?
>
> - make vim load plugin/*.py files with version hinting
>   if a file has a second line # python 2 or # python 3
>   vim will try to load those files with that interpreter.
>
>   if there is no hinting, use any (if enabled)

Reasoning for not implementing this this way is same as for autoloading
python/**.py: there are existing plugins that do not expect such behavior.
I would vote for some directory that is neither python/ (after some
thinking I find previous suggestion with __vim_init__ non-pythonic),
plugin/, autoload/, scripts?/ and so on: which is unlikely to hold python
files in existing plugins. Perhaps, pyplugin/?

> - keyboard interrupt for python !
>   Eg try :py while True: print "abc"
>
>   You cannot abort.
>
>   try the same in shell:
>
>   python -c 'while True: print "abc"'
>
>   press ctrl-c and you'll get:
>
>   Traceback (most recent call last):
>     File "<string>", line 1, in <module>
>     KeyboardInterrupt
>
>   I don't know whether this is possible. But if python would be much
>   more fun.
>
> I dont' know exactly which patches are pending, that's why I'm asking
> this way whether anybody is already working on those features?
>
> Marc Weber
>
> --
> --
> 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.
>
>

-- 
-- 
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.


Raspunde prin e-mail lui