> I remember you had your framework online. Did you remove it?
There has been no feedback nothing. So I stopped caring.
You can get it from git://mawercer.de/vl_repo.
(You all may also push your own branches there (even if they contain your
scripts).. Just don't put big binaries up!)
I'm using this .sh function to recreate all installers. You have to replace
*/vl_repo by the location of the repository.
createVimInstallers ()
{
rm -fr /tmp/installer;
mkdir /tmp/installer;
cd /tmp/installer;
gvim -v --noplugin -c "set runtimepath+=~/vl_repo" -c "silent! source
/home/marc/mwr/vl_repo/autoload/vl/lib/vimscript_installer/create_installer_examples.vim"
-c "silent! call
vl#dev#vimscript#vl_create_docs#CreateDocumentationFromDir('/home/marc/mwr/vl_repo/',
'/tmp/htmldocs')" -c "echo 'ready'";
for i in *;
do
zip ${i/.vim/.zip} $i;
done
}
Be aware that half of the code is rubbish.
(We can talk about wether , should be the beginning of a line as well
It just happens that I look more often at the beginnings than at the end.
That's why I like it :-)
Eg I've written my own abstraction over quickfix:
let formats = {
\ 'js' : [
\ '%E%f:%l: %m'
\ , '%-C:%l: %s'
\ , '%Z%s:%p^'
\ ],
[..]
which does automatically qoute the "," etc.. Because I never can
remember them.
It can be used like this: (this will do syntax checking of php files when
writing it.. terrible useful)
augroup PHP
autocmd bufread,bufnewfile *.php* setlocal ft=php
autocmd bufwritepost *.php* silent! call
vl#lib#quickfix#runtaskinbackground#RunInBGQF(['php','-l', expand('%')],{ 'efm'
: 'php', 'onFinish' : 'cw', 'loadErrorCmd' : 'cfile' })
augroup end
Of course the documentation thing is higly experimental and we can
change that. Ping me on irc (MarcWeber) if you have some free minutes so
that I can help you getting started. I'm also willing to remove all the
rubbish..
The German encyclopedia Brockhaus doesn't mention vim at all. It only knows
about the 30 year old vi! But it lists emacs as "the linux editor" *lol*..
It doesn't know that vim has been awarded serveral times..
> Sometimes, I have some feedback. But that's quite rare. Unless our scripts
> are exceptionally visible, we won't get much. Library oriented script seem
> to me to be the worse kind:
But it will be the only thing which will let us grow and enhance.
Because reading a library which is already well written and documented
can teach you very much.
> I did move my scripts to googlecode to track their evolutions, bugs and RfC.
> May be, I'll move them back to vim.org if it eventually offer what has been
> discussed in the other thread about vim.org and scripts hosting.
I've missed that thread. We don't need much. *One* git repository would be
enough. I can host it for free or we can use github..
Sincerly
Marc Weber
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
