You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
~ dead key immediately produce ñ on bepo layout #5238
But what I get instead is ñ is always immediately produced on dead key hit :
<altgr+n> -> ñ~
<altgr+n> -> ññ
<altgr+n> -> ñã
<altgr+n><altgr+n> -> ñ~~
If I do Remove-Module PSReadLine then all goes back to functioning as expected. (i.e the first <altgr+n> doesn’t produce any character, and the second hit produce the expected one.
Note that bépo layout has many other deadkeys, but this one seem to be the only one problematic.
Note that if I run the following : _Set-PSReadLineKeyHandler -Chord 'Alt+?' -Function WhatIsKey and then type <altgr+n> I get Ctrl+Alt+ñ: Key is unbound
I tried to "remap" this but neither of
I don’t know much about internals of this, but I would be happy to test / reproduce further stuff is useful. This issue is quite annoying to me.
Final note : once in neovim, hitting <ctrl+n> in insert mode results in weird binding I couldn’t fully identified, that somehow result in a <ctrl+n> caught by neovim
Expected behavior
No spurious ñ in my command line when I want to cd ~
Actual behavior
Keep trying to go to cd ñ~ which is not a place, therefore I’m sad ;-(
I gave this a try with other terminals, and noctty behaves the same than window terminal, but rio seems to work fine.
So it’s not a pure PSReadLine bug, seems to interact with the terminal somehow.... Or at least rio does something that fixes the weird behavior, walk around it ...
Ah, but if I do the WhatIsKey test above in rio, it dosen’t trigger at all when I type <altgr+n>, so at least it makes sense that it works. The dead key is never seen by PsReadLine
Activity
Yinameah commentedon Nov 17, 2026
Update :
I gave this a try with other terminals, and noctty behaves the same than window terminal, but rio seems to work fine.
So it’s not a pure PSReadLine bug, seems to interact with the terminal somehow.... Or at least rio does something that fixes the weird behavior, walk around it ...
Ah, but if I do the
WhatIsKeytest above in rio, it dosen’t trigger at all when I type <altgr+n>, so at least it makes sense that it works. The dead key is never seen by PsReadLine