We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would allow us to test e.g. https://risc-v-getting-started-guide.readthedocs.io/en/latest/zephyr-qemu.html
(although these actually come as scripts so it's perhaps not the best example)
anyhoo, the ability to test arbitrary HTML code snippets would be pretty rad
The text was updated successfully, but these errors were encountered:
We could focus (for now) on how Sphinx renders things. So basically unwrap all spans, and you're done.
Tabs like here: https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html are a difficulty, but if you properly extract the snippets, I don't think it really is.
Also, just came to my mind, in RST, naming the snippets that come in tabs could solve the problem, and the tabbed content is mostly generated anyway.
Sorry, something went wrong.
No branches or pull requests
Would allow us to test e.g. https://risc-v-getting-started-guide.readthedocs.io/en/latest/zephyr-qemu.html
(although these actually come as scripts so it's perhaps not the best example)
anyhoo, the ability to test arbitrary HTML code snippets would be pretty rad
The text was updated successfully, but these errors were encountered: