benpatridge

This works as expected, however it is very counter-intuitive. I would recommend making it so that you change the wording to 'do not preserve line wrap on copy'

Although it may be worth adding an option in the UI I was able to FINALLY find a workaround.

I added the following to my ~/.inputrc

# Home Key
"\e[1~": beginning-of-line
# End Key
"\e[4~": end-of-line

Exited and restarted a terminal session and now home/end work

This is still occurring even with RDM 2055.2.12.6

Have you found any workarounds?

I have a 2021 MacBook Pro 32G with Sonoma 14.5 with a Macally external MAC keyboard

I am using RDM 2024.1.8.6

I recently upgraded to Sonoma and it broke Karbiner Elements and my home/end key mappings no longer work.

Meaning I am unable to press the home key to go to the beginning of the line or the end key to go to the end of the line.

The only way I was able to home and end and shift/home shift/end it to work and correspond to CTRL-A (home) or CTRL-E (end) is to create

/Users/bpatridge/Library/KeyBindings/DefaultKeyBinding.dict with

{

 "\UF729" = moveToBeginningOfLine:;          // home

 "\UF72B" = moveToEndOfLine:;             // end

 "^a" = moveToBeginningOfLine:;          // home

 "^e" = moveToBeginningOfLine:;          // end

 "$\UF729" = moveToBeginningOfParagraphAndModifySelection:; // shift-home

 "$\UF72B" = moveToEndOfParagraphAndModifySelection:;    // shift-end

 "^\UF729" = moveToBeginningOfDocument:;           // ctrl-home

 "^\UF72B" = moveToEndOfDocument:;              // ctrl-end

 "^$\UF729" = moveToBeginningOfDocumentAndModifySelection:; // ctrl-shift-home

 "^$\UF72B" = moveToEndOfDocumentAndModifySelection:;    // ctrl-shift-end

 "^\UF702" = moveWordLeft:;                 // ctrl-left

 "^$\UF702" = moveWordLeftAndModifySelection:;        // ctrl-shift-left

 "^\UF703" = moveWordRight:;                 // ctrl-right

 "^$\UF703" = moveWordRightAndModifySelection:;       // ctrl-shift-right

 "^\U7F" = deleteWordBackward:;               // ctrl-backspace

 "^\UF728" = deleteWordForward:;               // ctrl-delete

 "^/" = "noop:";                       // ctrl-slash stops beep

}

That works in my apps including iTerm2 and terminal natively /etc.

However when I connect to the local mac by clicking on tools-->Terminal, or create an SSH Terminal to my local mac, the HOME and END key do not work.

If when in the RDM ssh (iterm2) session I press CTRL+a it does move the cursor to home

If when in the RDM ssh (iterm2) session I press CTRL+e it does move the cursor to end

If I open iterm2 natively home and end key do work as expected.

It works natively in terminal when I change the 'bash' keybindings to map the 'home' & end key to

\033[H

\033[F

If I click on an RDM SSH session to a Linux system using the same settings of my local mac terminal, Home and End DO work.

RDM Settings include:

1. The default Terminal set to iTerm2

2. SSH Shell is BASH

3. Home /End key mode: default (I have also tried standard)

It seems like when I ssh to 'localhost' which connects to my local MacTerminal it is not using iTerm2 or Terminal??

If you have any ideas let me know.

Thanks!

Yeah. If this comes back I will let you know. I haven't duplicated it lately. So you can close this issue for now.

Yes it occurs on any SSH Terminal.

I am unable to gather the logs because it hangs.

I am going to try to duplicate it again and will post more information.

Hello,

I have RDM 2023.3.13.4 on an Apple MacBook Pro M1 Pro 32GB Ventura 13.2

Since the past 3-4 updates I have consistently encountered the following problematic behavior:

I have SSH Sessions configured to my linux servers.

If I were to:

• "tail -f <logfile>" and there are many lines of text, the terminal will 'hang' and the mac will "beachball."

• 'cat <logfile' the behavior is the same

• unzip a file 'unzip <logfile.zip>' it also beachballs.

• Any activity in an SSH session where there are multiple lines of text scrolling across the screen the terminal session will hang.

Basically, instead of displaying the text to the screen scrolling by, the terminal will hang, beachball and possibly catch up.

More often I have to force-close RDM and restart RDM

I check Activity Monitor, and it is not an issue of memory or resources as I have plenty of CPU and memory available.

In Settings the 'Terminal Application' is set to iTerm2

This behavior does not happen if I natively use iTerm2

I have RDM 2022.2.15.0 and I have the exact same issue. Was something un-fixed or am I missing something??

Anytime I highlight text

When I paste it into my text editor it always adds a line wrap at the end instead of making it one contiguous line???

I have the following basic settings also.

I figured it out.

There isn't really much to show.

1. Double click on the filename "phonehome_archive_TGCS-160108-0464-20221018172335-0400-SupportBundle-Interactive.zip.never-uploaded"

2. It does not highlight it

3. Right click on the next line

4. It pastes as expected.

Upgraded to 2022.2.15.0 and set it back to Legacy=No and now it works.

It is interesting because previously when troubleshooting I was asked to set it Legacy=Yes.

I noticed that it does not highlight what you double click. Not sure if there is a setting for that, but I am glad it is working now.

One more question, when you make global preferences do you always have to exit all your terminals, close and restart RDM

I do not believe it is related but I was trying to figure out how make it so when I copy/paste log entries that it does not automatically add a carriage return upon pasting. I went over every single setting in RDM and iTerm2, and finally I found the answer and added it to my blog https://datastorageguy.com/2022/10/10/iterm2-adds-line-break-when-copying-text/

However, my current issue is:

in iTerm2 when I (for example)

Look at the following screen output

-rw-r--r-- 1 root root 16384015 2022-10-06 10:48 messages
-rw-r--r-- 1 root root  1428067 2022-09-11 00:01 messages-20220911.1662822061.gz
-rw-r--r-- 1 root root  1427877 2022-09-18 00:01 messages-20220918.1663426861.gz
-rw-r--r-- 1 root root  1427889 2022-09-25 00:01 messages-20220925.1664031661.gz
-rw-r--r-- 1 root root  1539657 2022-10-02 00:01 messages-20221002.1664636462.gz

If I double click on "2022" in log file name messages-20221002.1664636462.gz it will highlight the entire filename messages-20221002.1664636462.gz

However, when I go into RDM (and yes I have the Terminal set to iTerm2) and I double click the same log file it only highlights messages-20221002.1664636462.gz

I have the default "Double-click delimiters" set.

I have even tried adding a dash "-" by it self.

In iTerm2 under Preferences ---> "Characters considered part of a word" I have

/-+\~_.:

I verified the above delimiters are under my settings in RDM

/-_.!#$%&‘()*+,:;<>=?@[]\^`{}|~

When I compare iterm2 vs RDM using iterm2 for Terminal Application Type, after further testing, Ii appears the main issue is that RDM does not recognize delimiters

-:/.

Why that stopped working I am unsure?

Something broke in mine again? It very well could be my own fault but I have NO idea what may have changed??

I have RDM 2022.02.12.0

I am using Legacy Engine and the same setup I mentioned above.

I have terminal application set to iterm2

But I have also tried terminal

Ideas?

I have v2022.2.9.0

I was not using the legacy engine.

I did the following:

1. changed it to NO.

2. Closed and re-opened RDM

That worked!

That was the only 'feature' that bugged me. RDM is WAY better than Royal TSX!

I would add this to the support portal KB also.

*I also work in IT as an L2 Support Engineer! :-)

I still cannot get this to work on RDM 2022.2.9.0

in iTerm2 I have the default set as

 iTerm2->Preferences->General: "Characters considered part of a word: /-+\~_.".

And in RDM I have it blank

File --> Preferences --> Types --> Terminal --> Double-Click Delimiters

I have ALSO tried adding

File --> Preferences --> Types --> Terminal --> Double-Click Delimiters  --> /-+\~_.".

The results are the same.

I have closed/re-opened RDM and the results are the same.