cannot open square bracket

[hrvoje-grabusic]

Can't open square bracket [ when pressing ctrl+alt+f

On Croatian keyboard the left bracket is on the f key.

[majcherek2048]

Does it work if you use altgr instead?
How about when you disable the Bracket Matcher-plugin?

[hrvoje-grabusic]

it doesn't work with altgr+f.

I don't know how to disable bracket matcher.

It works if i remove this key binding
'.workspace .editor:not(.mini)': 'ctrl-alt-[': 'editor:fold-current-row'

So i guess this is not a bracket matcher issue im not sure where i should post this.

[majcherek2048]

There seems to be a lot of people with similar issues.
To me it looks like all of the individual issues have been collected in one:
atom/atom-keymap#35

Until it's fixed, you should be able to override it in your keymap file, or switch temporary to another keyboard layout.

[kevinsawicki]

Yeah, I believe the root issue here is atom/atom-keymap#35 as @majcherek2048 pointed out.

[VjeraTurk]

Year 2016, still not fixed

[RobbeVW]

A solution for my Belgian (nl_be) layout was to add the following code in the keymap (keymap.cson)
'atom-workspace atom-text-editor:not([mini])': 'ctrl-alt-]': 'unset!'

[ericpar]

I have the same problem using a French Canadian keyboard layout.

[rdemeyer]

The solution from @glowdemon1 works for me (layout fr_be).

[ghost]

Works also for me; thanks @glowdemon1

[koracIO]

Still having trouble @hrvoje-grabusic ?
I found this solution working for me, on my croatian keyboard:
'.platform-win32 .editor':
'ctrl-alt-f': 'native!'

'atom-workspace atom-text-editor:not([mini])':
'ctrl-alt-f': 'unset!'

[hrvoje-grabusic]

i am using visual studio code now.
It is interesting that vscode also had the same problem but they fixed it within a couple of days.
Since they open sourced it perphaps atom can copy their sollution.

[koracIO]

Would be nice if they did that.

[Smailowska]

@koracIO This helped. Thanks a lot!

[OptiZonion]

Thank you @glowdemon1 for the workaround. It would be nice to get a proper fix though...

[winstliu]

@dannybiker This should be fixed starting in Atom 1.12.0.