Re: Bug#590053: global.cgi fails to work with id-utils extension.

[Shigio YAMAGUCHI]

Hi,
> Feature-wise, I'd like to achieve following:
> 
> 1. Better support for server-less execution,
>    as a by-product of improved HTTP proxy compatibility.

You mean w3m support?

> 2. Generate custom HTML.
> 
>    Just as an example, I have a script using global that generates
>    output similar to "grep -A 10 -B 2". This prints lines before/after
>    matching pattern, and gives me better overview of caller/callee code.
>    It'd be nice to have this in HTML interface as well.

I think these functions are useful.

>    I think other people have their own favorite style of viewing,
>    so I'm not asking to include above interface. Instead, I propose
>    to add a hook to generate custom HTML.

Will the 'global.cgi' itself become a hook to do it?
It seems that all your plans above will be able to be achieved
by replacing global.cgi.

> With certain wrapper code, both can be done now - though not with ease.
> But with certain modification, these are fairly easy to support.
> Making these easier by default, I think, adds value to global.
> 
> Also, as Ron pointed out, instead of generating global.cgi everytime,
> having only one copy is nice (maintenance-wise). But that also means
> everyone will be affected when you customize that single copy. To avoid
> that, it's better to make some part run-time overridable with external
> configuration.

How about releasing your custom global.cgi (and style.css if needed) on your 
site?
It can be done independently of the main stream of GLOBAL.
I would like to link your site from GLOBAL's home page.
What do you think?
--
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3