diff options
| author | Sean Silva <silvas@purdue.edu> | 2012-10-10 17:07:23 +0000 |
|---|---|---|
| committer | Sean Silva <silvas@purdue.edu> | 2012-10-10 17:07:23 +0000 |
| commit | 9ce5c066260b221ddb35cfb8b2e7102f3fdabf0a (patch) | |
| tree | eb3a09147733faa4252d51e5432fd14629dd6e72 /lldb/scripts/Python | |
| parent | e999b865dd0edf005973fa01c82427563fcb4989 (diff) | |
| download | llvm-9ce5c066260b221ddb35cfb8b2e7102f3fdabf0a.zip llvm-9ce5c066260b221ddb35cfb8b2e7102f3fdabf0a.tar.gz llvm-9ce5c066260b221ddb35cfb8b2e7102f3fdabf0a.tar.bz2 | |
docs: Attempt to fix PR14053.
Hypothesis 1: use of `.. code::` directive instead of `.. code-block::`
is causing Sphinx to discard the block. On my machine, `.. code::`
renders fine. However, I don't think that `.. code::` is actually a
legit Sphinx directive. I believe that on my machine Sphinx is falling
back to just displaying it monospace with no syntax, whereas llvm.org's
Sphinx is just discarding it.
This is truly "remote debugging" since I can't reproduce this on my
machine. It would be helpful to be able to see the llvm.org Sphinx
build logs; if that's possible please let me know.
llvm-svn: 165632
Diffstat (limited to 'lldb/scripts/Python')
0 files changed, 0 insertions, 0 deletions