Skip to content
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.

Sign up for GitHub

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

Jump to bottom

text<space> inserted instead of <space>text after formatted text if a block has block-tags (org-mode) #9109

Closed
1 of 2 tasks
lef-est opened this issue Apr 15, 2023 · 2 comments
Closed
1 of 2 tasks

text<space> inserted instead of <space>text after formatted text if a block has block-tags (org-mode) #9109

lef-est opened this issue Apr 15, 2023 · 2 comments
Labels
editor :status/automatic-closing :status/automatic-stale

Comments

@lef-est
Copy link

lef-est commented Apr 15, 2023 •
edited

Search first

  • I searched and no similar issues were found

What Happened?

See gif:
　
GIF 2023-04-16 03-51-15
　
　
It happens after all kinds of formatted text, such as *bold*, /italic/, _underline_, [[page-ref]], ((block-ref)), {{cloze}} superscript^2 and subscript_2.
But only the last instance in the block is affected, i.e. if a block has two chunks of formatted text like:
test test *test* test test test /test/ test
The result will be
" test test test test test test testtest "

Expected Behavior

text should be inserted instead of text .

Desktop or Mobile Platform Information

This bug has always existed ever since I started using logseq about 2 years ago; Windows 10.

Are you willing to submit a PR? If you know how to fix the bug.

  • I'm willing to submit a PR (Thank you!)
@lef-est lef-est changed the title text inserted instead of text after formatted text if a block has block-tags (org-mode) text<space> inserted instead of <space>text after formatted text if a block has block-tags (org-mode) Apr 15, 2023
@cnrpman cnrpman added the editor label Apr 18, 2023
@github-actions
Copy link

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
@lef-est lef-est mentioned this issue Dec 12, 2023
Open
2 tasks
@lef-est
Copy link
Author

lef-est commented Dec 12, 2023

reopened in #10688

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
editor :status/automatic-closing :status/automatic-stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lef-est @cnrpman