It’s really frustrating. No-feature is better than poorly-implemented-feature.
Auto-pair is common in code editors and it woks seamlessly, because there are nuances how it should work, it’s not just doubling a character.
Say, I want to add backtick to finish line of code. I put the cursor to the end:
`const x = 1⎸
and type backtick. And Logseq puts two backticks:
`const x = 1`⎸`
It does not make any sense to add closing backtick when I’m at the end of the word! what makes it worse is that if I hit backspace, to delete one unnecessary backtick, it deletes them both.
So the only way to add a backtick at the end of the word is to:
- Hit backtick
- Hit right arrow to place the cursor after the second backtick
- Hit backspace to remove unnecessary backtick.
- Feel productive.
It is not helpful at all. And it’s not acceptable in tool for thought like Logseq, because it breaks the flow.
No feature is better than a broken feature.