-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Misidentifying ]p #48
Comments
Weird. It looks ok to me in both old and new Reddit. The fix for #47 replaces square brackets with fixed width square brackets which should not interfere with Markdown. Can you do an inspect element and see the generated HTML? |
On further inspection, it looks like it may be linking to the right place (
the comments in question in case you want to poke at it too. |
Yeah that is the correct markup. It works fine for me. Could it be that your font is missing the characters? Can you see the characters on this page? https://www.fileformat.info/info/unicode/char/ff3d/browsertest.htm |
Nice troubleshooting! I copied/pasted that from Firefox's view-source into the Github issue, and it didn't render the not-a-right-square-bracket there either, so I thought it demonstrated the issue. But looking at the same Reddit post and the Github issue-comment above in Chromium, that glyph does render correctly. So there's something about Firefox that fails to render that weird bracket. |
Created a comment with
:help ]p
and it linked to the help forp
instead of]p
FWIW, this feels familiar to #47, so like that issue, it might be an old-Reddit-only issue.
To Reproduce
:help ]p
p
insteadExpected behavior
VimHelpBot links to help for
]p
instead.The text was updated successfully, but these errors were encountered: