Reply to message «Re: google summer of code», sent 00:28:28 09 March 2011, Wednesday by Marc Weber:
> Why do you want to parse it? <...> > Didn't knew about this being a problem > Can you elaborate a little bit in which cases this bothers you > implementing signs? format.vim is an extensible text-to-markup (html/bbcode/latex, though only html targed is full-featured) translator. I do not want to place any signs, I want to get already placed by other plugins. > Can you give vim-addon-signs a try? I will probably read its code when I will create frawor/signs.vim module, but it definetly won't help me in getting signs placed by plugins that do not use vim- addon-signs. Original message: > Excerpts from ZyX's message of Tue Mar 08 21:08:06 +0000 2011: > > support to my format.vim plugin, but the following facts stopped me: > > 1. signs are accessible only with commands; > > 2. command output (which I may parse) is translated; > > Why do you want to parse it? > > Can you give vim-addon-signs a try? > > The idea is to declaratively tell Vim only about the state of signs > which must be placed. > All the update handling is done by the plugin. > This assumes that you have less than a million of signs to place though. > > This got rid of the annoying cumbersome api. > > But you're right rtp being a setting is bad. THere should be > setRTPList() and getRTPListk functions etc. > > > 3. v:lang variable value is system-dependent. > > Didn't knew about this being a problem > Can you elaborate a little bit in which cases this bothers you > implementing signs? > > Marc Weber
signature.asc
Description: This is a digitally signed message part.
