-
Notifications
You must be signed in to change notification settings - Fork 141
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
Missing Support for Python Console Output and Doctests #549
Comments
Where do these syntax definitions live? I poked around a little and
couldn't find them.
…On Fri, Aug 9, 2024, 11:46 PM Keith Hall ***@***.***> wrote:
I don't know of any sublime-syntax files which can currently highlight
doctests correctly. Theoretically if we were to create one, it would be a
lot easier to extend the base Python sublime-syntax to add support for it,
so probably we'd need to wait for #536
<#536> to be merged first
—
Reply to this email directly, view it on GitHub
<#549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA5E3INQBFYMWSHAMKMU7LZQWSLZAVCNFSM6AAAAABMJIRLXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZZGQ3TOOJVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Mainly in the Packages folder/submodule of the testdata folder: https://github.com/trishume/syntect/tree/master/testdata |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Syntect currently lacks support for highlighting Python console output (characterized by
>>>
and...
prompts) and doctests. This limitation hinders its ability to accurately represent Python code in various contexts, including code examples, tutorials, and interactive sessions.Expected Behavior:
Syntect should correctly highlight the Python code while ignoring the
>>>
,...
, and output (stacktrace or stdout).Steps to Reproduce:
Create a code snippet containing Python console output or a doctest:
Note this language is commonly called
pycon
(for python console), and tools like Pygments or Github markdown support this language (as evidenced by highlighting the above code).(My desire is because I'm exploring Typst and want like to port my books from LaTeX to Typst. See this bug typst/typst#4661 )
The text was updated successfully, but these errors were encountered: