-
Notifications
You must be signed in to change notification settings - Fork 58
need to press ":" twice in order to see it appear #39
Comments
|
|
Oh, right, and Capslock is mapped to ALT_L, so ALT_L + g produces ":" in my Layout. |
Could you post your custom layout somewhere? That will help us reproduce the problem. |
https://gist.github.com/epegzz/585158c5d88479edaa40 Here you go :-) |
maybe related to #37 ? |
The colon ( : ) is also not working on my keyboard either. How come this bug is from 30 Jun 2014 and wasn't closed yet? After 1 hour using Atom I thought it was going to be this time I was leaving Brackets :| Such a small bug and so big the annoyances caused. Makes it impossible to write CSS... |
@penafo which keyboard layout are you using? |
Sad to hear it's still not fixed. Was about to give Atom another try soon. |
Yeah, just saw that myself, sounds promising. Any idea when the current electron branch will be used in another Atom release? |
There's currently no ETA. Right now we're trying to update to the latest 0.36.x version, and then we'll probably start updating to 0.37.x. |
@50Wliu: Portuguese layout keyboard --> wikipedia image I already commented on #35 the problem that was originating it. Atom shouldn't allow external plugins to change users keyboard's "normal" keys in that manner.... allowing a plugin to change the function of a key as basic as the colon is going to kill the user-experience on Atom as a whole. Why not forcing all 3rd party plugins to use ONLY something like CTRL+SHIFT+somthing for theirs shortcuts and prompting the user to change them in case on install a new plugin some shortcuts "collide" with already registered shortcuts? |
When i press ":" the first time nothing happens. But when I type it one more time the ":'" appears.
Note: I do not use a default US layout. To Type characters like {}():;<>[] I use the capslock key plus a normal letter. All those mappings work fine with atom, except of the ":" which is mapped to Capslok + g (g = key code 0x29)
The text was updated successfully, but these errors were encountered: