-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
user template of output markdown file #6
Comments
What kind of template are you thinking about? I.e., what structure would you expect from such a template. Originally, I used pages generated by this plugin in Sphinx documents as includes, so that wasn't a use case for me, but I can see that could be useful in some cases. |
demo registerAddressMap
0x0 demo_name
0x0 r1
[return to module top](###0x0 demo_name) 0x1 r2
[return to module top](###0x0 demo_name) 0x2 r3
[return to module top](###0x0 demo_name) 0x3 r4
[return to module top](###0x0 demo_name) 0x4 r5
[return to module top](###0x0 demo_name) 0x5 r6
[return to module top](###0x0 demo_name) 0x6 r7
[return to module top](###0x0 demo_name) 0x7 r8
[return to module top](###0x0 demo_name) 0x8 r9
[return to module top](###0x0 demo_name) 0x9 r10
[return to module top](###0x0 demo_name) |
something like above, I would like to add some link to this, or put my description of field in the table, etc. I know this is not a mostly used structure of a register document, but maybe a way to add a template would improve the flexibility of markdown file. |
In order to generate a markdown document with user defined format, we may need an option to pass a template to the exporter. Do you have any plan to deal with it?
The text was updated successfully, but these errors were encountered: