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
While searching for a way to customize the highlighting in rich.markdown, I noticed that inline code themes didn't appear to be working correctly. Consider the following code:
from rich.console import Console
from rich.markdown import Markdown
console = Console()
console.print(Markdown("```\nTest\n```", code_theme="manni"))
console.print(Markdown("`Test`", code_theme="manni", inline_code_theme="manni"))
The expected output would be that both prints receive the code theme manni (it's redundant to use inline_code_theme if you have code_theme and you set it to the same, but leaving it out didn't change anything). However the actual result is the following:
To me this seems like a bug.
I also want to note that the docs of rich.markdown are very sparse.
Platform
Using Linux (Ubuntu 16), python 3.10.9 and rich 13.3.2. I also tried it in two terminals, both showed the same result (both have different color schemes too).
It seems like this is resolved, I think because I was using an older version of rich (possible in combination with newer version or way older version of some of richs dependencies).
Describe the bug
While searching for a way to customize the highlighting in
rich.markdown
, I noticed that inline code themes didn't appear to be working correctly. Consider the following code:The expected output would be that both prints receive the code theme
manni
(it's redundant to useinline_code_theme
if you havecode_theme
and you set it to the same, but leaving it out didn't change anything). However the actual result is the following:To me this seems like a bug.
I also want to note that the docs of
rich.markdown
are very sparse.Platform
Using Linux (Ubuntu 16), python
3.10.9
and rich13.3.2
. I also tried it in two terminals, both showed the same result (both have different color schemes too).Click to expand
The text was updated successfully, but these errors were encountered: