Unable to input certain characters about wsl HOT 46 CLOSED

Some kind of workaround: I noticed that pressing AltGr + 5 (that is [ on my french keyboard) then the desired combination (eg. AltGr + 6 for |) will input the character correctly. A bit tedious, though.

from wsl.

Hey guys, so the proper input and ALTGR+Key combination should be fixed and eventually make its way to the one of the next flights.

from wsl.

Awesome, it looks like the consensus is this is working in build 14352. If you encounter a keyboard layout that is not working as expected please let us know!

from wsl.

We were only supporting ASCII character set. I have just finished some work to extend it to UTF-8 and honor windows keyboard layout mapping, so in the future you could type special non-ASCII characters. We are still working on updating tty to properly support UTF-8 (especially in cooked mode) and are currently investigating why special keyboard combinations are not transmitting proper keycodes.

from wsl.

same thing with a french keyboard

from wsl.

This laptop has Swedish keyboard. It's only when using Bash I have this problem not Cmd, that AltGr doesn't work for typing @£${[]}~|. Swedish characters also doesn't work åäöÅÄÖ even though they don't use AltGr.

I tried this but it didn't work:

root@localhost:~# locale-gen sv_SE.UTF-8
Generating locales...
  sv_SE.UTF-8... up-to-date
Generation complete.
root@localhost:~# dpkg-reconfigure locales
Generating locales...
  en_US.UTF-8... done
  sv_SE.UTF-8... up-to-date
Generation complete.
root@localhost:~# dpkg-reconfigure console-data
Looking for keymap to install:
se-latin1
Deferring virtual terminal setup until console accessible.
root@localhost:~# dpkg-reconfigure keyboard-configuration
plymouth: ply-command-parser.c:939: ply_command_parser_parse_arguments: Assertion `loop != ((void *)0)' failed.
Aborted (core dumped)
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.103ubuntu4.3) ...

An idea is to have some script similar to raspi-config to configure keyboard etc, since normally in Ubuntu this is done using GUI tools, see https://github.com/RPi-Distro/raspi-config/blob/master/raspi-config

from wsl.

I'm on a desktop with Swedish keyboard, experiencing the same issues as other people in this thread.
I noticed however that @ebaratte's solution, typing AltGr+5 allows you to press a subsequent combination (e.g. the pipe character; reachable on my keyboard as AltGr+< (the key left of Z, to the immediate right of my left shift key).
This solution does not work for producing ÅÄÖ though... Also, when printing left bracket "[", the printed character isn't shown until the next key press (i.e. like thilde "~" or grave accent "`" normally does). Another interesting thing to note is that typing thilde (AltGr+¨, the key top left of Enter, to the right of Å) actually works without typing AltGr+5...

from wsl.

same with german keyboard AltGr (right alt key) doesn't work

from wsl.

Same here for the Norwegian keyboard. AltGr isn't working, making it much more difficult than it should be to produce symbols like @£$€{[]}

I've also noticed pressing AltGr+5 or AltGr+8 before the desired combination will force it to work as intended. It seems like AltGr+5 (which behaves just like Ctrl+Alt+5) is some kind of readline command. I'm in no way an expert in this, but Ctrl+Alt+5 and then pressing any number will produce (arg: [number]) . Not sure if this is helpful.

from wsl.

I also have this issue with a french layout, and it is still present in build 14328.
AltGr basically does not do its job when the terminal is running bash. Works fine as usual when cmd is running.

from wsl.

Also instead of being able to enter characters that I would be able to enter normally into anywhere else with my Hungarian keyboard, there are some combinations that instead seem to be doing something else.

E.g. AltGr + 1 for me is supposed to type out ~, but instead this appears:

root@AMCSI-ACER:~#
backup      games       landscape   lp          messagebus  pollinate   sshd        syslog
bin         gnats       libuuid     mail        news        proxy       sync        uucp
daemon      irc         list        man         nobody      root        sys         www-data

Or if I do AltGr + é (the location of é on the keyboard is the equivalent of ; on the US keyboard), instead of getting the expected dollar sign $, this gets outputted:

root@AMCSI-ACER:~#
_                BASH_SOURCE      HISTCONTROL      LESSOPEN         OSTYPE           SHELL
BASH             BASH_SUBSHELL    HISTFILE         LINENO           PATH             SHELLOPTS
BASH_ALIASES     BASH_VERSINFO    HISTFILESIZE     LINES            PIPESTATUS       SHLVL
BASH_ARGC        BASH_VERSION     HISTSIZE         LOGNAME          PPID             SSH_AGENT_PID
BASH_ARGV        COLUMNS          HOME             LS_COLORS        PS1              SSH_AUTH_SOCK
BASH_CMDS        COMP_WORDBREAKS  HOSTNAME         MACHTYPE         PS2              TERM
BASH_COMMAND     DIRSTACK         HOSTTYPE         MAILCHECK        PS4              UID
BASH_LINENO      EUID             IFS              NAME             PWD              USER
BASHOPTS         GROUPS           LANG             OPTERR           RANDOM
BASHPID          HISTCMD          LESSCLOSE        OPTIND           SECONDS

from wsl.

In Spanish, in addition to these symbols (eg '|'), you can not put accent marks

from wsl.

I think the problem is with ubuntu keyboard layout. Did you tried change that?
Probably something like this will help-
in bash type & install:

apt-get install console-common
Then you need reconfigure keyboard layout.
Try reboot PC.
There is many problems with this, I tried many methods, most of them don't work.

from wsl.

I think this is an issue with the newly improved Windows Console Host, it only seems to support US layouts for now.

I haven't noticed any such problems in cmd.

from wsl.

Thought I'd chime in with my findings on this. Turns out Asus GPU TweakII I have installed has global keyboard shortcut enabled for AltGr+2 (for the @ character). This introduces a slight delay in other programs when typing the keyboard combination as well, but the @ does show up. However, it seems like this slight delay somehow affects Windows Bash, as the character never appears.

Disabling the keyboard shortcut in Asus GPU TweakII resolved the problem in Windows Bash for me, but it seems like this could possibly be improved regardless (since, as mentioned, @ did show up after a small delay in regular applications).

from wsl.

The same happens with the portuguese layout.

But it's strange because, usually, **Alt _+ ( _Num6, **Num4 _) is a good replacement for _AltGr+2 to get @, but not in this case.

from wsl.

Same problem here with a French layout (azerty). I noticed that when bash is run from ConEmu, special characters are input correctly. Though arrow keys don't work anymore :(

from wsl.

Same issue with Danish keyboard layouts. I think this is an issue with the newly improved Windows Console Host, it only seems to support US layouts for now. Additionally, using an alternative console like ConEmu doesn't seem to work either (specifically arrow keys, del, ins, home etc.), presumably since bash.exe depends on some of those console host improvements.

from wsl.

Nor the PowerShell console. It's only on the bash console.

from wsl.

Note that trying to paste non-ascii characters in the console when bash is running also does not work.
Using ConEmu instead of the console let ascii characters be written with the keyboard including with AltGr key, but unlike on the previous build non-ascii characters now can not be entered at all, including under ConEmu.

from wsl.

Great! Thanks for the update!

from wsl.

This is still an issue in Build 14342, and now it's worse because preceding with AltGr+5 doesn't work, but one can use AltGr+8. I have Swedish keyboard.

from wsl.

It is possible that not all changes made it into this flight. Even when the fixes get in, sometimes they might slip into the next build.

from wsl.

working on 14352 😄, latinamerican keyboard configuration at least

from wsl.

@zerocool4u2 Were you able to accept the installation dialog with a Spanish localization?

from wsl.

@JorgeGT sorry man, i don't know what do you mean, the only thing that popups to my mind is the first installation of bash via lxrun, that was without missing characters for the spanish dialog like two versions ago and there is one shortcut i believe, alt+y, for accepting that installation...don't remember if i tried that.

from wsl.

Yes, I was referring to a known issue with the first installation where you
had to accept but instead of yes/no there were ???? and apparently you
couldn't accept. So no problems whatsoever installing / running bash?
Gracias! :)

El vie., 27 may. 2016 a las 12:35, Alexis Ramis ([email protected])
escribió:

@JorgeGT https://github.com/JorgeGT sorry man, i don't know what do you
mean, the only thing that popups to my mind is the first installation of
bash via lxrun, that was without missing characters for the spanish dialog
like two versions ago and there is one shortcut i believe, alt+y, for
accepting that installation...don't remember if i tried that.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABHIJ4nt8Q6dm7KjDiDr38mQZp8xT1cXks5qFsjagaJpZM4IByCU
.

from wsl.

yup no problems for me, but i'm using as the default language for windows Español-España, if there was an error somewhere maybe i missed because of that, i changed it to that one because many translations where missing on my local one, regards

from wsl.

It's working for me too!

from wsl.

working fine for french keyboard as well :)

On Fri, May 27, 2016 at 6:30 PM, Patryk Golus [email protected]
wrote:

It's working for me too!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AImcsoW-IfhhoaIK_OtSsUqr4AwLpOFYks5qFxwhgaJpZM4IByCU
.

from wsl.

I just installed the bash on the anniversary update. I have a German Windows and a German keyboard. I can enter special characters that require Alt Gr (such as [ or }) but I can't enter any umlauts (äöü)

from wsl.

Same here with Turkish Q layout, I can enter special characters with AltGr but can not enter Turkish characters: ğüşıöç.
Running build 14393.10

from wsl.

Still an issue with Norwegian keyboard layout. Pressing AltGr+2 should produce @, but gives nothing. AltGr+22 (pressing 2 twice) gives a new line with "(arg: 2)". AltGr+3 gives "�" (a square with questionmark in it, had to incresae font size to read it in bash window), should give £.

AltGr+4 gives $ correctly, same with AltGr+ 5=€, 7={,8=[,9=],0=} .. so AltGr+4 through 0 works fine. Same with AltGr+~.

Worth nothing that this is not a UTF problem as mentioned above. @ is well within he ASCII range (character 64).

(Running anniversary update)

from wsl.

Tip: To test this before sending the update just change keyboard layout in Windows to reported layouts and try pressing the reported combinations. I know it sounds basic, but seeing how someone managed to not do it in the multiple previous deployments I thought I'd mention it.

from wsl.

This seems to be fixed in the latest internal build.

from wsl.

Folks, still seeing the core dump issue with plymouth with the following

HP Pavillion
Windows 10 - Build 14931.rs_prerelease.160916-1700
Japanese Keyboard, English OS, Japanese Language Pack installed.

from wsl.

@wayne-kirk-schmidt: Could we open a separate issue for plymouth core dumping?

from wsl.

We can. Aside from the information above, I'm assuming we'd want the native Windows information on MUI, IME, and language. What else do we need?

from wsl.

Thats enough for start, thanks a lot @wayne-kirk-schmidt !

from wsl.

I have the exact same issue as @tedd with the Norwegian keyboard. AltGr+2 does not produce @ as expected, nor does AltGr+3 produce £, but instead a square �. This is with all Windows updates installed and Windows Bash installed for the first time today.

from wsl.

@asteinlein - This is a long post and difficult to keep track now. For quicker resolution, can you please open a new issue, following the template?

from wsl.

from wsl.

I have an Italian Layout ,
I am not able to pass any to bash Alt+/[digit]+/ or AltGr+/[digit]+/ sequemce .
For ex. Tilde ~ , via ALT+126 ,
copy/paste also does not work .

On Windows 10 Pro version 1703 build 15063.483
In Bash :
uname -a
Linux mypc 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux
lxd --version
2.0.10

from wsl.

I'm able to use altGr for everything except the top-left key on my keyboard; I have a custom version of the Swedish keyboard that replaces the default function of that key (which is usually §, ½, and no altGr character) to <, >, and |. The greater than/less than symbols work. However, when trying to input |, it inputs the § character instead.

from wsl.

Running NeoVim for windows in a cmd.exe in Windows Terminal, I cannot type a $ sign (AltGr+4) inside NeoVim. It does not work in the legacy cmd.exe terminal either.

from wsl.

I have this issue, I'm using WSL 1 with a Spanish layout.

from wsl.