Some characters inserted with AltgGr don't work

[vvollaro]

Version: 1.0.73
Platform: win32 10.0.17134
Plugins: none

On azerty keyboard, some additional characters can be inserted using a AltGr+Key (in fact the Alt key on the right). See this image for details for the french azerty layout for example.

In my case two keys are not correctly inserted, the characters ~ and `. For example when pressing the AltGr+é keys, the ~ should be displayed, but the é char is inserted instead. If I press space bar, the ~ is finally inserted.

When testing with the basic git bash window, the behavior is when pressing first the AltGr+é key, nothing is displayed, pressing bar space displays the "~" char. This the same behavior in Linux terminals:

[bahamut45]

+1 I have the same problem

[gdlx]

This is the same issue I opened on VScode: microsoft/vscode#68262

[gdlx]

Same issue with the ` character with AltGr + 7

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment.
Thank you for your contributions.

[bcxpro]

Still happens to me on the Spanish keyboard

[vvollaro]

I see that the microsoft terminal has the same problem and has a potential fix: microsoft/terminal#521

Maybe it is interesting to check their solution. Meanwhile, I use the combination of ctrl+alt instead and it works for me.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment.
Thank you for your contributions.

[vvollaro]

Always reproduced

[bcxpro]

Still happens to me on the Spanish keyboard

[gdlx]

Still relevant on 1.38.1 with French keyboard 😿

[fle108]

same problem on 1.0.91

[Renji-FR]

Me too on 1.0.103.3882.

[mr-potato-head]

Same problem on a french keyboard.

[Renji-FR]

A workround is to use Microsoft Keyboard Layout Creator to create a custom layout with tilde ~ configured without option "dead key". Under MSKLC, select ALTGR and make right click on ~ to unselect "Set as dead key"

[roonie007]

@Renji-FR Dude you are the best, I have been struggling with this since the problem started on VsCode

[Raton-Laveur]

Reproduced on VS Code 1.50.1 Win10 20H2. Regional settings are Windows display US, keyboard Azerty France.

[Eugeny]

I've just pushed a potential fix for these dead key related issues - would love to hear your feedback as soon as the nightly is built

EDIT: builds are up at https://github.com/Eugeny/tabby/actions/runs/1156041791

[enodr]

Just downloaded the windows portable version and unfortunately the fix does not work for me.

The xterm.js pull request you made to fix the issue has not yet been merged, has it?

[Eugeny]

@enodr dang. The fix isn't in xterm yet, but it's in tabby's fork.

[Eugeny]

@enodr I've just double-checked this with the current nightly on macOS and Windows and it works - are you sure you've grabbed the right version?

[enodr]

In fact on a AZERTY layout, with the current nightly build, only two keys don't behave correctly: the tilde ~ and the backtick `

The key "2" on a FR layout is:
2 (upper)
é (lower)
~ (need to press ALT-GR + space or ALT-GR + letter for ñ, õ, ã, etc)

When typing a ALT-GR + 2, Tabby outputs é and then after space press it outputs ~ and you now have é~ in the term instead of just ~. Same for backtick (key 7), you will end up with è`.

Unfortunately these two chars are keys used very often on linux terminal. Could that be yet another bug in xterm.js?

[bcxpro]

Just tested with this tabby-1.0.156-nightly.0-portable and my Spanish keyboard. AltGr+4 and then SPACE should display ~. It displays 4~

[Eugeny]

New potential fix available in the nightly: https://github.com/Eugeny/tabby/actions/runs/1167927546

GitHub

#768 - fixed altgraph modifier handling · Eugeny/tabby@fa66c96

A terminal for a more modern age (formerly Terminus) - #768 - fixed altgraph modifier handling · fa66c96

[enodr]

Well done it works!

[Eugeny]

Thanks for testing!

[bcxpro]

I just tested it on the Spanish keyboard. It definitely improved a lot but there is still an odd behaviuor.

This part is great:
AltGr+4 Space Expected: ~ Actual: ~
AltGr+4 a Expected: ã Actual: ã
AltGr+4 n Expected: ñ Actual: ñ
AltGr+4 o Expected: õ Actual: õ
all the characters like that seem to work fine now.

AltGr+4 i Expected: ~i Actual: ii
AltGr+4 p Expected: ~p Actual: pp
and so on...

It seems that for these characters that do not support a ~ above instead of displaying ~ and the character it duplicated the character.

[Eugeny]

Build ready: https://github.com/Eugeny/tabby/actions/runs/1177141278

GitHub

fixed #768 again · Eugeny/tabby@4ff5dea

A terminal for a more modern age (formerly Terminus) - fixed #768 again · 4ff5dea

[bcxpro]

Everything looks good to me now. El sáb, 28 ago 2021 a las 15:17, Eugeny ***@***.***>) escribió:

…

Build ready: https://github.com/Eugeny/tabby/actions/runs/1177141278 <https://repository-images.githubusercontent.com/77213120/49dde400-c8c2-11e9-812a-e1407f1f42af> <https://camo.githubusercontent.com/b6a12909f1e31185a69a73d59208c507a992236d3230f9fc18e85058ae3d19e7/68747470733a2f2f6769746875622e6769746875626173736574732e636f6d2f66617669636f6e732f66617669636f6e2e737667> GitHub *fixed #768 again · ***@***.*** <https://github.com/Eugeny/tabby>* A terminal for a more modern age (formerly Terminus) - fixed #768 <#768> again · 4ff5dea <4ff5dea> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#768 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3U6BGDL6HHYAFA2YSGQZTT7DOWVANCNFSM4HGSBVHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[enodr]

Works perfectly now, thanks.

[Bloopps]

Hi,
Sorry but for me the last nightly build does not fix the issue. #4433