>
>
> On Jul 15, 5:33 am, Masatake YAMATO <[email protected]> wrote:
>> Hi,
>>
>> How do you think putting the name of syntax into html file generated by
>> TOhtml?
>> Following patch does it.
>>
>
> What purpose does this serve? I'm not necessarily opposed to including
> it, but I'm not sure why it's needed.
Sorry, I didn't tell the backgroud of patch.
I'm developing web based source code viewer.
In the system vim is used in batch mode as html converter.
Converted html files are delivered through web server.
With javascript I'd like to provide some interactive commands working
on the generated html file. The behavior of commands will be changed
according to the ``syntax'' of original source code.
e.g.:
JUMP command works on
#include <bar.h>
in C syntax,
import foo.bar.Class;
in Java syntax, and
import foo.bar.Class
in python syntax...
If vim embeds the name of syntax to the converted html file, I don't
have to write syntax detector in javascript. Adding this feature is a
bit private request but similar type of software may want such
syntax(file type) information. So I submitted the patch here.
> At a glance, I don't see any problems with the patch itself, and the
> meta tag should not affect anything visible in a browser.
Yes! Only the javascript or something special processor will use.
> There is one difficulty, though, which your patch does not address.
> Recendly added in the version 7.3 runtime is the ability to generate a
> "diff view" which takes all diff'ed windows and puts them side-by-side
> in a table on a single page. This is a very nice feature, but what
> should we do for the syntax?
>
> It should be pretty easy to do a comma-separated list showing the
> syntax for each window. Would that meet your needs?
I'm using vim batch mode and in my purpose the diff feature will not
be used in my web based source code viewer. So embeding multiple
syntax names in to the meta tag is overspec for ME. If you mean you
will accept my patch if the patch handles the diff feature and embeds
the comma-separated list to generated html file, I will try to rewrite
the patch. But I'm really new to vim scripting, I may not do it well
quickly.
Masatake YAMATO
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
