aotto1968

There is already a good code parser I use for syntax highlight of __NON__ doxygen supported languages, it is called `source-highlight` > it would be fine if *doxygen* would support...

``` \section 1 \subsection 11 \subsection 12 \subsubsection 111 \subsubsection 112 \subsubsection 113 \subsection 13 ``` > you are in "112" topmost(first)=1 start=112 up=12 previous=111 next=113

everything could be possible → my mention was only the *minimum-requirement*. With the *minimum-requirement* I can generate all the other movements with a combination of these *minimum-requirement* **example:** 1. the...

You are always free to add more specific `\navigation` elements than described in the previous requirement.

well today my Bitcoin-ABC destroy my Bitcoin-CLASSIC database… because after automatic restart…(using the option set on configuration)… the "datadir" commandline option from the previous start was NOT set… and Bitcoin-Cash...

can NOT say that "bitcoin" are lost… I use this system only as node…

I think you have a problem with error-reporting → I miss a switch like *-debug* to gather all information you need and make it for the end-user maximum easy to...

I found a partial work-around → I take the "tag" file and filter-out the NOT wanted part with a POST-processing shell script. I try some xml-editor examples but finally end...

It is primary a *doxygen* problem because the `...` (2) section has nothing todo with vim-plugin. in (1) you can decide between to have a RIGHT `doxygen`-output OR to have...

simple code example for `*.doc` file, try to get *html* generation from ~~~~ /** "have some fun" /* a comment */ "finish" **/ ~~~~