Do you (or have you in the past) had iTerm2 installed on this machine?

If so, I believe this is because iTerm customizations (due to enabling Shell Integration) to the environment are not compatible with a native Xterm terminal. There are escape sequences that don't mean anything to an Xterm; they end up resulting in the display of the garbage since SecureCRT doesn't know how to interpret the iTerm2 specific customizations (and SecureCRT shouldn't be expected to know how to handle these custom-to-iterm2 sequences).

Since only iTerm (or other "in-the-know" apps) can interpret the customized escape sequences, you will need to follow instructions on disabling iterm2's Shell Integration, or have a Logon Action in SecureCRT for your local shell connections (the default session) to do something like below (YouTube video demonstrating Default Session):

I have added this thread to a feature request in our product enhancement database for an option for SecureCRT to nicely handle the customizations associated with iterm2's Shell Integration. Should a future release of SecureCRT include this feature, notification will be posted here.

If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #13279" in the subject line or use this form from the support page of our website.

I'm still trying to figure out where to change the prompt of the local shell. Is it in the Advanced in Terminal Session Options? If so, what do I put in and where?

Quote:

Originally Posted by bgagnon

Hi waynespa,

Do you see the same issue in Mac's native Terminal app?

Do you (or have you in the past) had iTerm2 installed on this machine?

If so, I believe this is because iTerm customizations (due to enabling Shell Integration) to the environment are not compatible with a native Xterm terminal. There are escape sequences that don't mean anything to an Xterm; they end up resulting in the display of the garbage since SecureCRT doesn't know how to interpret the iTerm2 specific customizations (and SecureCRT shouldn't be expected to know how to handle these custom-to-iterm2 sequences).

Since only iTerm (or other "in-the-know" apps) can interpret the customized escape sequences, you will need to follow instructions on disabling iterm2's Shell Integration, or have a Logon Action in SecureCRT for your local shell connections (the default session) to do something like below (YouTube video demonstrating Default Session):

I have added this thread to a feature request in our product enhancement database for an option for SecureCRT to nicely handle the customizations associated with iterm2's Shell Integration. Should a future release of SecureCRT include this feature, notification will be posted here.

If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #13279" in the subject line or use this form from the support page of our website.

Changing your local prompt is something that is typically handled outside of SecureCRT. The commands/formatting needed to change your prompt will vary depending on the Operating System you are running on.

What Operating System are you using?

Can you elaborate on the changes you are trying to make? What is your prompt displaying now? What would you like your prompt to be?