Skip to content

Fix cypher's comment matching (and add one keyword) #2504

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

Merged
merged 3 commits into from
Sep 19, 2023

Conversation

Axolord
Copy link
Contributor

@Axolord Axolord commented Sep 10, 2023

Previously, comments matched the whole line, no matter what.
Now they only match everything after '//'.

Also fixes #1364.

Furthermore, single quote strings are now also valid.

Copy link
Contributor

@jeanas jeanas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@jeanas
Copy link
Contributor

jeanas commented Sep 19, 2023

Looks like I told myself I'd merge after CI passed and just forgot; sorry.

@jeanas jeanas merged commit 483d550 into pygments:master Sep 19, 2023
@Anteru Anteru added the A-lexing area: changes to individual lexers label Nov 17, 2023
@Anteru Anteru added this to the 2.17 milestone Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-lexing area: changes to individual lexers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CypherLexer double forward slash in string is always a comment
3 participants