bug: Enabling pymdownx line numbers globally also renders them in signatures #192

Activity

1. pawamoy

   added

   bugSomething isn't workingSomething isn't working

   on Oct 14, 2024
2. pawamoy

   self-assigned this

   on Oct 14, 2024
3. pawamoy commented on Nov 26, 2024

   

   pawamoy

   on Nov 26, 2024

   MemberAuthor

   More actions

   OK, easy fix. I also decided to do the opposite for pycon code examples in docstrings (the ones written without fences) and to start respecting highlight's configuration. Commit message:

   The reasoning is that someone enabling line numbers globally supposedly also wants them for code blocks in docstrings. There's in my opinion no difference between a code block in a Markdown document and a code block in a docstring, they both serve documentation purposes and should be subject to the same rendering rules.

   If that makes someone unhappy, we can always consider adding an option to hide line numbers for code blocks in docstrings.
4. pawamoy

   added 2 commits that reference this issue on Nov 26, 2024

   fix: Respect highlight's `linenums` config for `pycon` examples in do…

   ...

   53eb82a

   fix: Never render line numbers for signatures and attribute values

   ...

   a669f1c
5. pawamoy

   closed this as completedon Nov 26, 2024
6. viktorlashchuk

   added 2 commits that reference this issue on Feb 24, 2025

   fix: Respect highlight's `linenums` config for `pycon` examples in do…

   ...

   0527487

   fix: Never render line numbers for signatures and attribute values

   ...

   bcf0855