I support (and have asked elsewhere) this feature because it’s current imposing on users is not useful on so many levels:
-
it is not Context-Aware: If I only want to close a previous opened character from the auto-close map, put it only once there, not twice. Then, if I select some text and type a character from the Map, enclose the selected text with that character, as expected;
-
I want to be able to edit the whole auto-close sets map and keep what I find useful and remove what I find frustrating and not useful to me. For example, I would like that
[[
to trigger not[[]]
but[]( [[]] )
so I can have astandard Markdown Link
that also uses the Logseq Link Feature. After Auto-Completion, keep the cursor between the first [] just as with Links and then, if I type Enter or Tab (interchangeably) it should jump in between the Logseq Page Link square brackets; -
I find it frustrating to use Logseq with Text Expanders when trying to Expand some text that has in it whatever characters from this auto-closing map because it ends up a messed up text with no sense. See Anybody using Espanso with Logseq? If so, how do deal with "replace" strings that contain [, (, etc -> which auto-complete the closing corespondent?;
Bottom line: I want to be able to Independently Toggle OFF the auto-closing characters feature and the Selected Text Enclosing feature as well as UNITE the Auto-Close feature with some internal Text Expanding feature so I can define not only what character sets will get auto-closed but what the end-format will look like just like with text expanders.