On Nov 10, [EMAIL PROTECTED] wrote:
> vim... I'll try to get it more polished/functional and put it up on
> sourceforge or somewhere.
Change "sourceforge or somewhere" to:
http://www.vim.org/scripts/add_script.php
--
_ _ ___
|V|icah |- lliott http://micah.elliott.name [EMAIL PROTECTED]
" "
[EMAIL PROTECTED] wrote:
> 2. Failing that, look in a help dictionary; I generated mine from the
> info version of the Python docs, using a simple Python script.
Which is as follows (run on all the python-lib*info* files and it'll
generate a file called "output"; rename that to ~/.vim/pyhelp.py)
Christoph Haas wrote:
> But Vim scripting looked even evil for me... and
> I've been working with Perl for a decade. :)
Vim scripting is nasty, but thankfully you don't really need to use it
any more. You can write all your code in python with just a one-line
hook to map it to a key.
On the topic
Hi, Roman et al...
On Thursday 10 November 2005 00:52, Roman Roelofsen wrote:
> The last 5 days I´ve been working on a code-completion/calltips plugin
> for vim. It´s working pretty good but not finished yet. I will anounce
> the first beta version on this mailling list. I hope during the next
> w
Roman Roelofsen wrote:
>>Evening,
>>
>>Is there a decent way to get that help into vim? Or like showing docstrings
>>or help that I get through pydoc on request? I've been working myself
>>through a pile of vim macros/plugins but couldn't find even one which
>>simplifies programming in Python. Furt
> Evening,
>
> Is there a decent way to get that help into vim? Or like showing docstrings
> or help that I get through pydoc on request? I've been working myself
> through a pile of vim macros/plugins but couldn't find even one which
> simplifies programming in Python. Further issues would be han
