Tagged: alt key
December 3, 2015 at 10:04 #9234
I have a number of ALT related keyboard mappings in Emacs on Linux that I use quite frequently. There is an already knows open issue that has been filed for this problem:
It is currently marked as ‘minor’ but this is more along the lines of a major irritation for me as I’m constantly swapping between windows and NX session and getting bitten by this bug. Effectively I end up inserting random characters into the current buffer I’m working on, some of which I end up not noticing and then get compile errors due to these errant keystrokes.
I’d like to request that this be updated to ‘normal’ at least because I fear that anything in the ‘minor’ state is probably not going to get any attention for quite a long while.
My guess is that many users are effected but don’t know it’s this bug causing these strange random effects where ALT is ignored the first time it is used after switching to the NX session.December 3, 2015 at 17:39 #9253BritgirlKeymaster
The fix for that is actually planned for the next release, so currently going through QA.December 15, 2015 at 09:02 #9342wernermaesParticipant
Same problem here.
Looking forward to solution.
Werner MaesJanuary 5, 2016 at 18:26 #9561
This didn’t seem to make it into the 5.0.58 release. Brit, can you give an update on this, and preferably update the priority to ‘normal’.January 11, 2016 at 16:28 #9614TorContributor
Our recent release was mainly focused on mobile platforms, so some fixes didn’t go through all required testing and were delayed to the next release.
Nevertheless if you want to test our version including this fix, just contact us on forum[at]nomachine[dot]com.January 15, 2016 at 23:45 #9682
Thanks! Yes, I’d be willing to beta test a fix for this. I just set a note to the address you mentioned.January 28, 2016 at 16:50 #9854
Just tested the TR08M05960 patch you sent this morning. Unfortunately, I’m not able to connect to my NX session with the patched binary so haven’t been able to test if this is fixed. I get the following error message when I try to connect with the patched binary with existing profiles.
Could not connect to the server.
Error is 22: Invalid argument
I also triead creating a ‘new’ profile but I got the same error message.
I’ve attached the session logfile.January 28, 2016 at 16:55 #9857BritgirlKeymaster
Send the logs directly. They may have been too big to upload here.February 1, 2016 at 09:10 #9889
Hi Brit, I found the problem – I was still on 5.0.43 and didn’t realize there had been an update to 5.0.63 so was applying the patch to the wrong release.
I did some initial testing, trying ALT and non-alt key combinations after Atl-tab transition to NX window and so far I haven’t seen any issue. I’ll continue using the release today and update this topic if I do see any problems.
This topic was marked as solved, you can't post.