|
57 | 57 | % 4- while still allowing expansion of Pygments latex mark-up |
58 | 58 | % Other aspects such as framing, caption handling, codeline wrapping are |
59 | 59 | % added on top of it. |
60 | | -% Perhaps we could cease using fancyvrb and implement 1, 2, 3, 4 by own |
61 | | -% pure LaTeX code. This would allow in particular to wrap long code lines |
62 | | -% in a manner allowing a pagebreak in the middle. But dropping fancyvrb |
63 | | -% and keeping its native features and those we added by hacking into it |
64 | | -% would be a significant effort. |
| 60 | +% Perhaps we could cease using fancyvrb and implement 1, 2, 3, 4 by own pure |
| 61 | +% LaTeX code. But dropping fancyvrb and keeping its native features and those |
| 62 | +% we added by hacking into it would require a significant effort. |
65 | 63 | \RequirePackage{fancyvrb} |
66 | 64 | % Next line is in order to let TAB characters (ascii 9) obey tab stops, |
67 | 65 | % MEMO: attow (2025/12/26), a TAB can not be found inside a code-block |
|
371 | 369 | % HTML interprets the argument of :emphasize-lines: as referring to effective |
372 | 370 | % line numbers in output (i.e. first line is always associated with number 1 |
373 | 371 | % even though the actual printed line number, or the original line number in |
374 | | -% the source may differ, due to seeting of :lineno-start:). This is why we do |
| 372 | +% the source may differ, due to setting of :lineno-start:). This is why we do |
375 | 373 | % not use here \c@FancyVerbLine, but resort to \FV@CodeLineNo, for PDF output |
376 | 374 | % to follow same rules as HTML. |
377 | 375 | \newcommand\sphinxFancyVerbFormatLine[1]{% |
|
0 commit comments