Databases
StackOverflow2013
Postsdbo
POCygwin non-US or indirect characters don't work in xterm on extra monitor
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCygwin non-US or indirect characters don't work in xterm on extra monitor
    text
    copied!<p>I have run into this freaky thing in two places now, on a Windows 7 and an XP machine.</p> <p>I have a laptop with an extra monitor connected. I start up cygwin's x-server, using the start menu shortcut (Cygwin-X/XWin Server). I then start an xterm by right-click the X icon in the icon tray at the bottom right, and selecting Applications/xterm.</p> <p>I get an xterm. In it I can type text, but depending on which monitor the xterm window resides, all characters that require two keypresses on my swedish keyboard (example: "~" requires me to first press alt+the key marked "^ ¨ ~" and then press space, rendering a single ~ on the screen) result in a space being printed.</p> <p>If I move the xterm to the other monitor, I am suddenly able to type a ~ in the xterm. Move it back to the previous monitor, and I can't type ~ anymore.</p> <p>Weird or what? This is the problem I have now, on my XP laptop. On my Windows7 laptop (same basic setup) I had the problem that I could only type stuff like åäö (not indirect/combined characters - I have keys marked å, ä and ö respectively on my keyboard) on one monitor, not the other.</p> <p>I have messed around with different ways to start up the X Server, I think I am doing it the right way as I describe here.</p> <p>My cygwin installation is maybe a year old on both machines. I would like to be able to find whatever setting causes this behaviour, so I can handle it should I come across similar problems in the future.</p> <p>Any ideas?</p> <p>Edit: some stuff that looked like html tags got mangled.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload