You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Really thank you for providing this library.
I hope this will overcome my usage issues with recommonmark also in the long run.
It would be helpful, if .. mdinclude:: /_static/whatever.md would always starts looking on the doc root level (where sphinx-build command is executed) when reference starts with /.
This would match the behaviour of sphinx's ..include: directive.
The text was updated successfully, but these errors were encountered:
Does anyone have a workaround for this? I can't really make good use of this plugin otherwise.
It seems like passing in something like .. mdinclude:: /source/imports/file.md results in the directive looking at the /source from the fs root instead of the project root.
I don't actually see anything different in how mdinclude handles finding the file compared to Include :
The code looks the same, but both directives behave completely differently. I don't know nearly enough about Sphinx API to dig much further than this :/ cc @CrossNox - I'd take a look at this but I'm not really sure what would be causing this behavior given how similar the code is between Include and MdInclude.
Really thank you for providing this library.
I hope this will overcome my usage issues with recommonmark also in the long run.
It would be helpful, if
.. mdinclude:: /_static/whatever.md
would always starts looking on the doc root level (wheresphinx-build
command is executed) when reference starts with/
.This would match the behaviour of sphinx's
..include:
directive.The text was updated successfully, but these errors were encountered: