-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fixes #27605: inline math blocks can't be preceeded/followed by alphanumerical characters #30175
Merged
silverwind
merged 7 commits into
go-gitea:main
from
jmlt2002:fix-inline-math-blocks-preceeded-followed-alphanumeric-chars
Apr 2, 2024
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1edf43a
Fix #27605: inline math blocks can't be preceeded/followed by alphanu…
jmlt2002 e375bf3
Add 2 test cases
jmlt2002 88f41f3
Allow math expressions to be preceeded but not suceeded by alphanumer…
jmlt2002 eb7546e
Allow math expressions to be suceeded only by punctuation.
jmlt2002 774e664
Merge branch 'main' into fix-inline-math-blocks-preceeded-followed-al…
GiteaBot 6c95855
Merge branch 'main' into fix-inline-math-blocks-preceeded-followed-al…
GiteaBot 15abbcc
Merge branch 'main' into fix-inline-math-blocks-preceeded-followed-al…
GiteaBot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could there be a case for something like:
$a a\\$b b$
=>?
In case the users would like to escape and use
$
I have this question because I guess the old code might work with
$a a\\$b b$
(although it reports errors for$a a$b b$
, it is still acceptable)So I'd like to confirm the new code's behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old code does what you described with
$a a\$b b$
, with only one backslash. With two, or any even number of backslashes it would generate an error.With the current code, the expression
$a a\\$b b$
generates the expression below.If the user wanted to get the output that you described he would need to use the following expression
$a a \$ b b$