Hyper: Entering a "~" / "`" symbol does not work with German keyboard

[swernerx]

I have a iMac with a German keyboard. Entering the tilde symbol using the normal key shortcut alt+n does not work. The same with the backtick symbol "" itself which is placed after theß` symbol.

There is also some issue with the dollar sign (shift+3). This jumps a word to the beginning instead of entering the symbol.

HyperTerm 0.7.1
Electron 1.2.8
darwin x64 15.6.0

[MrRio]

Hi there, Could you try the master version? If you follow the contribute instructions in the README, that should get you going.

[crunchtime-ali]

@MrRio I have the same problem and just tried it with the current master (518b0cd9a5dfe883048d1e460ed4b6ce750b8879). We still can not enter ~

This is also a duplicate of https://github.com/zeit/hyperterm/issues/213

[MrRio]

Can you do

git fetch
git checkout debug-keyboards

Then View -> Toggle Developer Tools.

If you could press each of those keys and paste me the output

[MrRio]

oh, and npm run dev && npm start

[crunchtime-ali]

This is the output:

{
  altKey : true,
  code : "KeyN",
  key : "Dead",
  metaKey: false,
  shiftKey : false
}

[MrRio]

Try this branch https://github.com/zeit/hyperterm/pull/584

[MrRio]

The fix-international-tilde branch should sort the tilde issue, the others I need output for, and if they're not the same across all keyboards we may either have to ask the OS for the keyboard layout, or wait for https://github.com/zeit/hyperterm/pull/214 to land

[crunchtime-ali]

Awesome, #584 works with the german keyboard layout:
However the "`" still doesn't work.

The debug-output of ´ is {"key":"Dead","code":"Equal","shiftKey":false,"metaKey":false,"altKey":false}"
The debug-output of is{"key":"Dead","code":"Equal","shiftKey":true,"metaKey":false,"altKey":false}"`

[thomas-alrek]

I am just buzzing in to say that I experience the same issue on a Norwegian keyboard layout (MacBook Pro 2012)

[crunchtime-ali]

@alrek-consulting Have you tested #584 ?

[onbjerg]

Same with Danish keyboards as well.

[crunchtime-ali]

C'mon people. This repo feels almost like Facebook or the YouTube comment section.

@onbjerg & @thomas-alrek Plese checkout #584 and say whether it fixes the tilde for you. If that or reading the few comments in this issue too much work for you better don't say anything at all.

[onbjerg]

@dj-hedgehog Relax. I tried and I had the same issue as you. No need to be rude, at all.

I was merely pointing out that it was ALSO an issue for Danish keyboards (even on #584), which I think could aid in debugging, but I don't know. It has also been a long-standing issue in Atom.

[crunchtime-ali]

We're well aware that this is an issue with Danish (#213), Swedish, Norwegian etc. keyboards as well.

Can you try

git fetch
git checkout debug-keyboards

and give us the output of the non-working keys?

[MrRio]

It's a lovely sunny Monday over here in the UK. Let's keep it nice. 😀🌞

[crunchtime-ali]

In Germany its cloudy with no chance of ´ & ` working in HT :disappointed_relieved:

[wcastand]

Hi, i'm on a mac with a french keyboard:

I tried to git checkout debug-keyboards and i still can't use "~" or "`"

[crunchtime-ali]

@wcastand The branch debug-keyboards only shows the keys you pressed in the console. Feel free to post these for the not-working combinations here!

[wcastand]

Hey, sorry my bad :/
this is the result of the console log for "~" :

KeyboardEvent {isTrusted: true, key: "Dead", code: "KeyN", location: 0, ctrlKey: false…}

And for "`":

KeyboardEvent {isTrusted: true, key: "Dead", code: "Backslash", location: 0, ctrlKey: false…}

If you need all the object, let me know :)

[jnsdrtlf]

It seems like this issue was fixed with the release of 0.8.1.

[bellstrand]

Still not working in 0.8.3 with a Swedish keyboard (mac).

{
    isTrusted: true,
    key: "Dead",
    code: "BracketRight",
    location: 0,
    keyCode: 221,
    keyIdentifier: "Unidentified"
} ... and more

[pcalves]

This issue could probably be closed in favor of #29. Everyone interested in this should also subscribe to #214 which looks to provide a fix for this! 🙌

[AndersonFirmino]

I have the last version 0.8.3 and this bug remains im my Linux Mint :cry: