TOVL = the one vim lib.
The lib is an very early stage and much has still to be done. But let me
tell you what the main goals are and let me invite you taking action and
help me expand and enhance it.
If you don't have much time jump in and try:
(You may want to remove ~/.theonevimlib_config afterwards)
$ git clone git://mawercer.de/theonevimlib
add the contained core folder to your runtimepath:
set :runtimepath+=theonevimlib/core
and restart vim. Then execute
:TOVLConfig
You should see something like this:
============= snip ===================================================
dictionary=
example:dictionary=
commandName:string=ExamplePluginH
command:string=echo 'lo world to you from example plugin'
loadablePlugins:dictionary=
example:number=1
[### your editing config file /home/marc/.theonevimlib_config ##### ]
============= snip ===================================================
Try
:Help
to get more info. It tells you how to play with the example plugin
redefining a very simple command or removing it if you unlead the
plugin.
So what is this all about?
I feel vim.org is nice but the vim community is lacking one feature:
Something thate ruby, perl, php all do have: A way to get plugins fast
and automatically. Yes there is vimball. But it did never adress all
problems. Most of the plugins do contain mappings of the author. You
customize them, you update the plugin and your changes are lost. TOVL
tries to separate functionality (the lib part) from user interface
(configuration). Using a version control system such as git you'll be
able to up and dowgrade on the fly if something has gone wrong.
TOVL can evolve to a vim community project:
* get all the code at once but only run the code you really want
That's done by activating "plugins"
disk is cheap, your time is not!
* containing most useful scripts, mappings, code without bloat
Because using a git repository everyone can commit to and remove
or enhance code. This should result in a very nice vim library
everyone likes to work with.
* Make people starting to learn vim more productive because they
can jump in and enable those plugins without the need to
read all the vim tips.
* no longer waste dev time rewriting the same stuff again and again.
(such as template systems etc).. We should try to get all features
into one "plugin" and enhance that. I think there is still enough
which can be improved.
* maybe integrate a dependency system to create isntaller only
adding the library files which are actually needed.
(Some of the code is already there. But I still have to clean it up)
* don't ever override configurations by accident while running
multiple vim instances. Configuration changes are written to
disk and reloaded by the other instances automatically.
* more to be done.
Of course a lot of things are still missing in the configuration
editor: highlighting, completion, ... I'll add featuers piecwise.
(Maybe you want to help me?)
Please read the top level README and tell me about your feelings?
It is still a prototype. I need your input to make it even better.
It may become a replacement of most scripts. But at the beginning I'd
like to make it only a collection of exsisting scripts.
Sincerly
Marc Weber
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
