Unexpected rendering of block references in parentheses

da5nsy commented 1 year ago

Search first

[X] I searched and no similar issues were found

What Happened?

I often like to reference blocks in parentheses.

I'm working on a foo (block reference to issue) and it's going dreadfully etc.

I keep on getting tripped up by the odd (IMO) rendering when doing so.

Reproduce the Bug

This text:

- This is going to get referenced
  id:: 64a1f4fb-a0fe-4a79-abb1-753f5dff028d
    - No spaces (((64a1f4fb-a0fe-4a79-abb1-753f5dff028d)))
    - Space at start, not at end ( ((64a1f4fb-a0fe-4a79-abb1-753f5dff028d)))
    - Space at end, not at start (((64a1f4fb-a0fe-4a79-abb1-753f5dff028d)) )
    - Space at both start and end ( ((64a1f4fb-a0fe-4a79-abb1-753f5dff028d)) )

is rendered as:

Expected Behavior

I'd really like it if option 1 worked...

Screenshots

No response

Desktop or Mobile Platform Information

App Version: 0.9.10 Git Revision: 16c472b Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.9.10 Chrome/104.0.5112.124 Electron/20.3.8 Safari/537.36 Language: en-US

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!)

da5nsy commented 1 year ago

The analogous arrangement of parentheses works for this type of link...

[This is going to get referenced](((64a1f4fb-a0fe-4a79-abb1-753f5dff028d)))

github-actions[bot] commented 8 months 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!

da5nsy commented 8 months ago

This is still relevant as of:

App Version: 0.10.3 Git Revision: c491914 Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.3 Chrome/118.0.5993.159 Electron/27.1.3 Safari/537.36 Language: en-GB Plugins: harmony-theme (v.1.3.0), logseq-cusgit-theme (1.3.2), logseq-flow-nord-theme (v0.9.32), logseq-ozean-theme (v0.1.1), logseq-dracula-theme (0.0.5), logseq-pdf-export-plugin (2.2.8), logseq-oxford-blue-theme (v0.2.0), logseq-tabs (v1.19.1), logseq-block-to-page (v1.3.0), logseq-emoji-picker-fork (v0.0.5), logseq-dev-theme (v1.26.17), logseq-graph-analysis (0.10.2)

logseq / logseq