Can't include `}` character inside /cloze

clayms commented 6 months ago

Search first

[X] I searched and no similar issues were found

What Happened?

I can't include a } character in a /cloze. Examples:

{{cloze `}` }}
{{cloze `\}` }}
{{cloze `\\}` }}

all of which do not work.

Reproduce the Bug

Try putting the } character inside a {{cloze }}

Expected Behavior

Have some kind of escape character before the } so the cloze ignores the ending brace character.

Screenshots

No response

Desktop or Mobile Platform Information

OS: Linux x86_64 Kernel: 6.6.2-arch1-1 App Version: 0.9.20 Git Revision: unknown Platform: Mozilla/5.0 (X11 Linux x86_64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.9.20 Chrome/114.0.5735.289 Electron/25.9.3 Safari/537.36 Language: en-US Plugins: logseq-bullet-threading (v1.1.4), logseq-journals-calendar (v0.10.10)

Additional Context

No response

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

[X] I'm willing to submit a PR (Thank you!)

clayms commented 6 months ago

Is this the function that parses the cloze?

https://github.com/logseq/logseq/blob/6fbf6c0520dde82497f715af834a83c6704164f7/src/main/frontend/handler/export/html.cljs#L137

github-actions[bot] commented 5 days ago

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, 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!

logseq / logseq