Skip to content

Markdown lexer improvements#1623

Merged
Anteru merged 5 commits intopygments:masterfrom
Leistungsabfall:feature/improve-markdown-lexer
Jan 6, 2021
Merged

Markdown lexer improvements#1623
Anteru merged 5 commits intopygments:masterfrom
Leistungsabfall:feature/improve-markdown-lexer

Conversation

@Leistungsabfall
Copy link
Copy Markdown
Contributor

@Leistungsabfall Leistungsabfall commented Dec 7, 2020

This is a series of improvements to the Markdown Lexer:

  • Fenced code was not recognized when it contained empty lines
  • Inline code was not recognized after bulleted list entry (e.g. * `code` )
  • Bold and italics were not recognized when surrounded with non-space char (e.g. (**foo**))
  • There is no way to recognize code indented by 4 spaces using regex only - so remove the error-prone detection

@Leistungsabfall Leistungsabfall changed the title Feature/improve markdown lexer Markdown lexer improvements Dec 7, 2020
@Anteru Anteru added this to the 2.8 milestone Dec 8, 2020
@gerner
Copy link
Copy Markdown
Contributor

gerner commented Dec 17, 2020

I verified that the perf issue described in #1617 is fixed by this change with identical output from pygmentize on the test file. If this PR gets merged then my proposed fix in #1618 is unnecessary.

@Anteru Anteru modified the milestones: 2.8, 2.7.4 Jan 6, 2021
@Anteru Anteru merged commit 811f1a6 into pygments:master Jan 6, 2021
@Anteru Anteru self-assigned this Jan 6, 2021
@Anteru Anteru added changelog-update Items which need to get mentioned in the changelog and removed changelog-update Items which need to get mentioned in the changelog labels Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants