Using Byobu and F-keys
I'm trying to use SSH with byobu enabled. It's a tmux/screen window manager, which uses F2 to create a new window and F3/F4 to navigate through those windows.
But in RDM, when I press either of these keys, it just pastes a tilde (~) into the prompt.
I've already stumbled upon this post: https://forum.devolutions.net/topics/23795/using-f-keys-in-ssh-sessions
There, one of the staff members suggests to use the keyboard-settings to customize the layout. But I'm not really sure how that's supposed to help. There are no screen/tmux keyboard shortcuts that can be assigned there. I've also went through the list and unassigned all instances of the F2-F4 key that I could find, but this didn't help either.
I was able to get the desired behavior, by going to a sessions properties and setting the "Function keys mode" (under the keyboard tab) to "Xterm".
Great, but I obviously don't want to do that for all of my sessions. Where can I change the default behavior? I went through the settings but there are no entries to set the function keys mode globally. I don't really understand, the default function keys mode for all sessions is literally called "Default". So what does Default mean? Shouldn't I be able to set the default in the settings?
I saw that I can technically export all of my sessions to an XML file and then use a script to add "<FunctionKeysMode>Xterm</FunctionKeysMode>" to every entry.... but I'm hoping there is a simpler ways of doing it
All Comments (3)
Hello Ryan,
Thank you for getting in touch with us. To better assist you, could you kindly provide us with the following information:
- Your current RDM version.
- The data source you are utilizing.
To set the XTerm on multiple session at once, I would suggest to use the Batch Edit option. To do so, select all your SSH entries by using the CTRL+LEFT-CLICK or SHIFT+LEFT CLICK and do a right-click and select Edit > Batch Edit > Edit entries (Session type settings) > Keyboard > Check the Override options and set the XTerm.
Here's a helpful topic about the Batch Edit option if needed.
https://docs.devolutions.net/rdm/kb/how-to-articles/batch-edit-rdm/#batch-edit
Also, I would suggest to create a template for your next SSH entry that you might create later. With this template you will be able to set the Xterm option "per default."
Here's a helpful topic about the Template if needed.
https://docs.devolutions.net/rdm/commands/file/templates/creating-templates/
Also, under the File - Options - User Interface - Keyboard after changing the F keys have you tried to change the "Mode" to see of this would work?
Thank you for letting me know. If you have any other questions, feel free to let us know.
Best regards,
Maxim Robert
Your current RDM version.
2024.3.17.0 64-bit
The data source you are utilizing.
Local/Offline
Also, under the File - Options - User Interface - Keyboard after changing the F keys have you tried to change the "Mode" to see of this would work?
When I change the mode manually, the F-keys work. Even without unassigning them under the User Interface -> Keyboard
To set the XTerm on multiple session at once, I would suggest to use the Batch Edit option. To do so, select all your SSH entries by using the CTRL+LEFT-CLICK or SHIFT+LEFT CLICK and do a right-click and select Edit > Batch Edit > Edit entries (Session type settings) > Keyboard > Check the Override options and set the XTerm.
Here's a helpful topic about the Batch Edit option if needed.
https://docs.devolutions.net/rdm/kb/how-to-articles/batch-edit-rdm/#batch-edit
Also, I would suggest to create a template for your next SSH entry that you might create later. With this template you will be able to set the Xterm option "per default."
Here's a helpful topic about the Template if needed.
https://docs.devolutions.net/rdm/commands/file/templates/creating-templates/
I see, that's good to know. Thank you, that worked! 👍
I didn't realize you could batch-edit them.
----
However, I just found (a completely unrelated) bug in RDM:
When trying to import sessions from MobaXterm, it only imports sessions that have the default icon. If you set the icon to something else, then they're not recognized/imported in RDM.
When you export all of your MobaXterm sessions to file, then a line with the default icon looks like this:
test=#109#0%192.168.1.1%22%%%-1%-1%%%22%%0%-1%0%%%-1%0%0%0%%1080%%0%0%1#MobaFont%10%0%0%0%15%248,248,242%39,40,34%255,128,0%0%-1%0%%xterm%-1%6%0,0,0%85,85,85%249,38,114%221,66,120%166,226,46%157,197,75%230,219,116%209,202,137%102,217,239%122,204,218%174,129,255%179,146,239%0,217,217%200,240,240%245,222,179%255,255,255%80%24%0%1%-1%<none>%%0#0#
And a session with a non-default icon looks like this:
test=#144#0%192.168.1.1%22%%%-1%-1%%%22%%0%-1%0%%%-1%0%0%0%%1080%%0%0%1#MobaFont%10%0%0%0%15%248,248,242%39,40,34%255,128,0%0%-1%0%%xterm%-1%6%0,0,0%85,85,85%249,38,114%221,66,120%166,226,46%157,197,75%230,219,116%209,202,137%102,217,239%122,204,218%174,129,255%179,146,239%0,217,217%200,240,240%245,222,179%255,255,255%80%24%0%1%-1%<none>%%0#0#
The only difference being the number 109 at the beginning, which stands for the default icon. I'm not sure why that is. Every entry with another number than 109 will not get imported into RDM. It seems like a bogus bug. Not a big problem, but yeah.
Hello Ryan,
For the MobaXTerm issue I took a look at the code, and the start of the string seems to be related to the type of entry it is. In your first scenario, we interpret #109#0 as an SSH terminal entry.
There's a few other we support:
#98#1 = telnet
#91#4 = RDP
#128#5 = VNC
#130#6 = FTP
#140#7 = SFTP
#84#9 = Files/Documents
#313#11 = Web browser
Any other type is unhandled. In your case, what is the entry that contains the value "#144#0" mapped to in MobaXTerm? It's probably possible to add this to the import if we have a matching type to import as on our end.
Regards,
Hubert Mireault