You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When typing, I press ctrl+i to start typing in italics. logseq inserts two 's and moves the cursor between them, as with auto-closing parentheses or brackets. I type what I want to be italicized, then to close the italics, I press ctrl+i again to terminate the italiced string, as I would in a word processor. Instead of jumping to the right of the * (which is what happens if I type ''), logseq inserts two more *'s, and puts the cursor between them.
Reproduce the Bug
Press ctrl+i while typing
Type a string
press ctrl+i again
same behaviour happens with ctrl+b for bold, etc.
Expected Behavior
the second ctrl+i should move the cursor to the right of the final *, as if I manually typed *
Screenshots
No response
Desktop or Mobile Platform Information
Kde Neon, Linux app, 0.8.18
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
I'm willing to submit a PR (Thank you!)
The text was updated successfully, but these errors were encountered:
Search first
What Happened?
When typing, I press ctrl+i to start typing in italics. logseq inserts two 's and moves the cursor between them, as with auto-closing parentheses or brackets. I type what I want to be italicized, then to close the italics, I press ctrl+i again to terminate the italiced string, as I would in a word processor. Instead of jumping to the right of the * (which is what happens if I type ''), logseq inserts two more *'s, and puts the cursor between them.
Reproduce the Bug
Expected Behavior
the second ctrl+i should move the cursor to the right of the final *, as if I manually typed *
Screenshots
No response
Desktop or Mobile Platform Information
Kde Neon, Linux app, 0.8.18
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: