Xshell Forum

Tilda character not working ?

Last post: Monday, March 16, 2015 8:01 PM by Support, 5 reply

 
Thursday, January 29, 2015 2:24 PM - Bob

Tilda character not working ?

 
I am running the latest version of Xshell 5. Whenever i ssh into any Linux server the tilda character (key to the left of 1) does not work. Is anyone else having that problem ?

Thanks

Program Ver. : Xshell 5
Monday, February 2, 2015 2:58 PM - Support

Re: Tilda character not working ?

 
Please answer the following questions:

1. Which font are you using?
2. What is the encoding settings on Xshell and the remote host? ('echo $LANG')
3. Can you try changing the font and see if the problem persists.


---
Technical Support
Tuesday, February 3, 2015 10:24 AM - Bob

Re: Tilda character not working ?

 
I am using Terminal, tried switching to other fonts same issue.

Xshell Encoding: Default Language (i am running Win 7 x64, US), remote host en_US

If i start a brand new instance of Xshell and connect to the same host, tilda character is working (then eventually it stops).
Tuesday, February 3, 2015 10:32 AM - Bob

Re: Tilda character not working ?

 
Here is more information for you. I can re-produce it very easily now.

My computer has two monitors. When i RDP into another computer and my RDP session is set to "Use all monitors", when i start Xshell on remote computer tilda character works if Xshell is on the left monitor but as soon as i move Xshell window to the monitor on the right, tilda character stops working. All other characters work just fine.
Tuesday, February 3, 2015 12:15 PM - Bob

Re: Tilda character not working ?

 
Forgot to add that RDP session is initiated from a Mac using Microsoft Remote Desktop client (version 8.0.12, OSX 10.10.2)
Monday, March 16, 2015 8:01 PM - Support

Re: Tilda character not working ?

 
We have tested this issue with Macbook Pro (OSX 10.10.2) and RDP client 8.0.14 and connected to Windows 8.1 with multi-monitor enabled. However, the problem did not occur. Please try upgrading RDP client first and try again.

Also, can you try the test on a different machine? I think this problem might be an isolated incident.

---
Technical support