Hi,
This probably another Caps Lock problem with remote desktop applications. I am an emacs user and I have made Caps-lock key an additional control key on both of my computers (using similar settings as http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2 ). All my computers are running Mate desktop 1.8 and Caps-lock key work as expected (i.e. as ctrl) on both computers on local session. However, when I am connected to the other computer using x2go pressing caps-lock key seem to do nothing at all on remote session - pressing caps-c just prints lowercase c in terminal (& in emacs). Checking the output on xev on remote session does show keycode 66.
This issue is really getting into my work flow as I am a heavy emacs user. Is there a solution or workaround? Could using a custom ~/.xmodmap resolve the issue? I just want caps-lock key to always work as ctrl and I am fine with totally getting rid of caps-lock behavior.
PS: Thanks a lot for developing x2go. It is really convenient piece of software.
Thanks, CB
Chitresh Bhushan wrote:
Hi,
This probably another Caps Lock problem with remote desktop applications. I am an emacs user and I have made Caps-lock key an additional control key on both of my computers (using similar settings as http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2 ). All my computers are running Mate desktop 1.8 and Caps-lock key work as expected (i.e. as ctrl) on both computers on local session. However, when I am connected to the other computer using x2go pressing caps-lock key seem to do nothing at all on remote session - pressing caps-c just prints lowercase c in terminal (& in emacs). Checking the output on xev on remote session does show keycode 66.
This issue is really getting into my work flow as I am a heavy emacs user. Is there a solution or workaround? Could using a custom ~/.xmodmap resolve the issue? I just want caps-lock key to always work as ctrl and I am fine with totally getting rid of caps-lock behavior.
PS: Thanks a lot for developing x2go. It is really convenient piece of software.
Thanks, CB
Using kde, I configure both local and remote desktop to use caps lock as additional control key, and have no problems.
Okay, after a lot of hit and trial, I can now reliably reproduce the issue:
Both local and remote desktop are running Linux mint 17 with Mate 1.8.1. Both are configured to use caps lock as additional ctrl key.
Does that sound like a bug? Here are version details:
On local:
X2Go Client V. 4.0.2.1 (Qt - 4.8.6)
On remote: $ x2goversion x2goagent: 3.5.0.27 x2goserver: 4.0.1.15 x2goserver-xsession: 4.0.1.15
-- CB
On Tue, Aug 12, 2014 at 4:25 AM, Neal Becker <ndbecker2@gmail.com> wrote:
Chitresh Bhushan wrote:
Hi,
This probably another Caps Lock problem with remote desktop applications. I am an emacs user and I have made Caps-lock key an additional control key on both of my computers (using similar settings as http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2 ). All my computers are running Mate desktop 1.8 and Caps-lock key work as expected (i.e. as ctrl) on both computers on local session. However, when I am connected to the other computer using x2go pressing caps-lock key seem to do nothing at all on remote session - pressing caps-c just prints lowercase c in terminal (& in emacs). Checking the output on xev on remote session does show keycode 66.
This issue is really getting into my work flow as I am a heavy emacs user. Is there a solution or workaround? Could using a custom ~/.xmodmap resolve the issue? I just want caps-lock key to always work as ctrl and I am fine with totally getting rid of caps-lock behavior.
PS: Thanks a lot for developing x2go. It is really convenient piece of software.
Thanks, CB
Using kde, I configure both local and remote desktop to use caps lock as additional control key, and have no problems.
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user