Never mind, I was being dense:
svn checkout http://lh-vim.googlecode.com/svn/map-tools/branches/1.0.0/
lh-vim-read-only


On Oct 18, 8:36 pm, 703designs <[EMAIL PROTECTED]> wrote:
> Wow, that's one robust plugin you're developing (very impressed by the
> inclusion of ft-specific settings). I browsed the source, and tried to
> check it out, but I get a 404:
>
> svn: URL 'http://lh-vim.googlecode.com/svn/trunk'doesn't exist
>
> Just wanted to let you know. Could you email me lh-map-tools.tar.gz
> for 1.0? My only alternative is to manually download each raw file...
>
> Thanks,
> Thomas
>
> On Oct 18, 8:09 pm, Luc Hermitte <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > "703designs" <[EMAIL PROTECTED]> :
>
> > > Following this tip:
> > >http://vim.wikia.com/wiki/Automatically_append_closing_characters#Imp...
>
> > > I've pasted the code three times, replacing ( with [ and {, ) with ]
> > > and } respectively for the latter two.
> > > [...]
> > > Any ideas as to how I could extract the second
> > > mapping into a function, taking one argument for the matched
> > > character?
>
> > The first version of my bracketing system was quite impossible to evolve 
> > and maintain. In the last version (*), I've provided a command that helps 
> > define normal-, visual- and insert-mode bracket-mappings.
>
> > (*) The v1.0.0 is only available through subversion at that 
> > moment:http://code.google.com/p/lh-vim/wiki/lhBrackets
>
> > Otherwise, you have several options:
> > 1- play with :exe to map with options
> >    :exe "inoremap <silent> ".open." ".open.close."<left>"
>
> > 2- Have a function that execute the mapping itself ; the function will play 
> > with exe+normal
>
> > 3- Have an <expr>-mapping that expand the result of the called function.
>
> > HTH,
> > --
> > Luc Hermittehttp://lh-vim.googlecode.com/http://hermitte.free.fr/vim/
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to