Remove escaped underscores, backticks, and brackets from Google Docs exports#13
Merged
hsbt merged 1 commit intoruby:masterfrom Feb 24, 2026
Merged
Conversation
Member
|
@paracycle Unfortunately, this change is conflicted by other PR. Can you update with the current HEAD? |
paracycle
force-pushed
the
fix-escaped-underscores
branch
3 times, most recently
from
d7d2040 to
628b993
Compare
…exports When meeting logs were exported from Google Docs to Markdown, several characters were unnecessarily escaped with backslashes: Escaped underscores (539 instances, 49 files): to\_s -> to_s, \_\_FILE\_\_ -> __FILE__, rb\_cFixnum -> rb_cFixnum Escaped backticks (83 instances, 28 files): \`foo\` -> `foo` Escaped brackets in code/text context (63 instances, 22 files): \[1, 2, 3\] -> [1, 2, 3], hash\[key\] -> hash[key] Note: escaped brackets in ticket references (e.g. \[Feature ...\]) are intentionally left unchanged for a separate cleanup. Files affected span 2013-2022, with the majority in 2014-2019.
paracycle
force-pushed
the
fix-escaped-underscores
branch
from
628b993 to
d4edf78
Compare
Contributor
Author
|
I've rebased this on latest |
hsbt
approved these changes
Feb 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When meeting logs were exported from Google Docs to Markdown, several characters were unnecessarily escaped with backslashes.
Escaped underscores (539 instances across 49 files):
to\_s→to_s,each\_char→each_char\_\_FILE\_\_→__FILE__,rb\_cFixnum→rb_cFixnumEscaped backticks (83 instances across 28 files):
\`foo\`→`foo`Escaped brackets in code/text context (63 instances across 22 files):
\[1, 2, 3\]→[1, 2, 3]hash\[key\]→hash[key]\[PATCH\]→[PATCH],\[ANN\]→[ANN]Note: Escaped brackets in ticket references (e.g.
\[Feature ...\]) are intentionally left unchanged for a separate cleanup.53 files changed spanning 2013-2022.
Disclosure: I am trying to make sure all Meeting Notes are formatted correctly, and using LLMs to help me do that. Changes have been made by Claude Opus 4.6, but reviewed by me.