Vim normal mode: typing "{" enters "{}" instead of sending the command to Vim (French keyboard)

Steps to reproduce

Start in Vim normal mode.

Type { (on a French keyboard on Mac, at least). On a Mac, this is done by typing Option-(, where ( is on the same key as 5.

Expected result

Vim should go to the beginning of the current paragraph.

Actual result

Instead Obsidian inserts the typed character, as a block (“{}”).


  • Operating system: macOS Ventura 13.1
  • Debug info:
    Obsidian version: v1.0.3
    Installer version: v0.15.8
    Operating system: Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103 22.2.0
    Login status: not logged in
    Insider build toggle: off
    Live preview: on
    Legacy editor: off
    Base theme: dark
    Community theme: none
    Snippets enabled: 0
    Restricted mode: on

Additional information

The problem is the same for similar characters like [, } and ]. It likely comes from the fact they require some key modifiers (like Option, in this case), on non-US keyboards.

PS: a similar problem happens with the ^ command (start of line): on a French keyboard, typing a ^ is obtained by pressing the ^ key followed by a space (so as to indicate that no letter goes underneath). This works in vanilla Vim, but not in Obsidian’s Vim mode (where ^ is inserted even when starting in normal mode—Vim starts by doing this too, but then switches to beginning-of-line when following this with a space).

This seems similar to this bug, which was fixed in the upstream vim plugin here. Looks like the fix could be similar.

1 Like

Oh, looks like it has already been fixed: Curly braces and @ not working · Issue #56 · replit/codemirror-vim · GitHub, mentioned on Obsidian forum here: When will a fix upstream be integrated into obsidian?

1 Like

Thanks. I had a look at the references. If I understand correctly, such bugs are fixed but the fixes are not published yet?

This has been fixed upstream for simple movements, but not yet for complex combos.

For things like ci[, see International keyboard fix for opt-[key] · Issue #71 · replit/codemirror-vim · GitHub.

1 Like

It hasn’t yet been updated in Obsidian.

1 Like

should be fixed in 1.1.14. Let me know if it works.

1 Like

Great. Will do, when it’s publicly released!

I confirm that this works in 1.1.15, thanks a lot!!

For reference, there are other issues related to non-QWERTY keyboards, such as the backtick (`) for jumping to a mark or the caret (^) for going to the first non-blank character, which are not recognized as commands (but are instead inserted as text), but I understand that this is an issue that’s outside of Obsidian’s direct control.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.