-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Use rst_prolog and rst_epilog only for rst files? #2445
Comments
No, that makes a lot of sense. Should be a bugfix for 1.4.2. |
I might want to apply replacements in markdown for example (using recommonmark or similar), so it would be actually nice to preserve some way to do replacements on non RST. I wasn't actually even getting the rst_epilog to work on markdown though so I am not sure if it's just me or not but this would be a nice-to-have for markdown :) |
Fixed at 9cd5ba9. BTW, |
Apparently, Sphinx adds those to all source files, regardless if those are actually reST files or not.
This leads to problems with some custom
source_parsers
, e.g. spatialaudio/nbsphinx#38I think
rst_prolog
andrst_epilog
should only be prepended/appended for actual reST files.Is there anything speaking against this?
The text was updated successfully, but these errors were encountered: