I guess from the way you described how you use dead keys, it sounded like you didn't know the "correct" way to get get the result you want or maybe that your computer was configured in a weird way that is causing you trouble.
I would never "double press backtick" as that would leave the last backtick in "modifier-mode" and depending on what character you type next it would merge or not.
E.g. your example of "back-tick, back-tick, a" should result in à and not`a as you describe (provided that your dead key setup is functioning properly).
The proper/best way to type a back-tick on a keyboard with dead keys is "back-tick + space" - and that should work in any app.
Looking closer at your screen capture, it looks like your back-ticks are transformed into a completely different set of characters when you type two back-ticks in a row.
Errata : the issue seems to not have originated from VSCode but from a bad font on my side. Strange that it only acted like this with VSCode, but that was definitely not their fault !
I guess from the way you described how you use dead keys, it sounded like you didn't know the "correct" way to get get the result you want or maybe that your computer was configured in a weird way that is causing you trouble.
I would never "double press backtick" as that would leave the last backtick in "modifier-mode" and depending on what character you type next it would merge or not.
E.g. your example of "back-tick, back-tick, a" should result in
à and not`a as you describe (provided that your dead key setup is functioning properly).The proper/best way to type a back-tick on a keyboard with dead keys is "back-tick + space" - and that should work in any app.
Looking closer at your screen capture, it looks like your back-ticks are transformed into a completely different set of characters when you type two back-ticks in a row.
Does back-tick + space work for you?
Errata : the issue seems to not have originated from VSCode but from a bad font on my side. Strange that it only acted like this with VSCode, but that was definitely not their fault !
Great that you figured out what the issue was!