Not if the language is standardized from the start.
An alternative would be a language with a simpler syntax. Something like XML, but less verbose.
Have you read the CommonMark specification? It’s very complex for a language that’s supposed to be lightweight.
Markdown is terrible as a standard because every parser works differently and when you try to standardize it (CommonMark, etc.), you find out that there are a bajillion edge cases, leading to an extremely bloated specification.
I think all of those suggestions are feasible. However, what should the plugin do in situations when a delimiter is deliberately left unclosed, such as character literals? I wouldn’t want it to permanently suggest the corresponding closing delimiter.
That’s an interesting idea. How exactly would you imagine it to work?
It did ask for my e-mail.