Hi, When I copy an email into logseq, I often get an identifier that contains a segment with am embedded hash sign, e.g., abcdefg#12345. Unfortunately, logseq ends up turning the #12345 into a tag. Is there a way to change this behavior such that a tag is not created in an embedded case?
I cannot change the parser, but if you want I could possibly automate one of your current solutions. Would you be willing to use a different key combination for preprocessing of the pasted text? If so:
Which solution would you prefer?
What about replacing the character with a similar one (maybe the sharp ♯)?
Which key combination would you like?
Could you provide a bigger example with a couple of email references?
I tend to drag the message into logseq rather than copying it.
The problematic part of an item looks something like this: imap-message://gyro.xxx%40gmail.com@imap.gmail.com/INBOX#191824.
I suppose that wrapping in backticks would be best, but that is not difficult to do by hand.
I just wish that native logseq would handle this issue better.