I must have been looking in all the wrong places

[venta]

Does anyone know much about doxygen?

I am generating a whole bunch of html files from some C++ headers. The per-function documentation pages I get out all have the following element:

<div class="navtab">
....
</div>

which forms a sort of sidebar-style index to all the other functions whose docs were generated from the header.

I don't want this to be present. I thought that GENERATE_TREEVIEW=NO in the config file would suppress it, but it doesn't. (At least, it doesn't using doxygen 1.5.4 or 1.7.4, and I can't find any references online to it being broken. So maybe that isn't what that switch is meant to do, though it sounds like it in the docs.)

DISABLE_INDEX=YES also isn't the right answer - that disables a different bit of auto-generated guff which I also don't want.

Does anyone:
(a) know what GENERATE_TREEVIEW actually governs?
(b) know what switch I need to set to suppress this sidebar-index thing?
(c) as a last resort, have any ideas of how to painlessly remove a div element and all its contents from an html document? (I have no experience of Perl or anything like that, though I suspect I may be about to acquire some if (b) cannot be solved.)

Auxiliary comment: no, I can't just hide the div element using CSS. Well, I can, obviously. But it's not good enough. I actually need that element removed from the html.

Comments

[venta.livejournal.com]

I think the regex you will need then is...

Thanks. I'll have a look at that if I don't get any sense from the doxygen forum I also sent the question to earlier today - if not generating the div in the first place is an option, I'd sooner go with that.

do a replace in files

This will have to be done every time the files are autogenerated, from a makefile. So it needs to be a bit less human-assisted than that :) Once I've comprehended that actual regexp, then hopefully I can communicate it to sed and do it that way.

[mister-jack.livejournal.com]

I'd check it works manually first ;)

[venta.livejournal.com]

Nah, what can possibly go wrong...

(That came under the 'comprehending' part ;)

Cheers.

[venta.livejournal.com]

hopefully I can communicate it to sed

This will be a waste of time, Elizabeth. Sed is purely line-based and won't match over linebreaks.

[bateleur.livejournal.com]

Personally I take the view that millions of programmer hours worldwide could be saved if sed was removed from every system by default. That way nobody could every think "I have sed and not perl on this system, so I'll try doing it with sed".

[venta.livejournal.com]

My argument is "I know how to use sed[*] I don't know how to use perl, so I'll try doing it with sed". However, if your plan had been implemented I probably wouldn't be in that situation!

[*] For certain limited values of "know" and "use".