You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
I know that you can change the window title using Window > Behaviour | Window title, but this field is either static (when Terminal > Features | Disable remote-controlled window title changing is checked) or replaced all the time by a remote escape code.
The problem is, I want to have full domain names in my window title somewhere and yet keep the remotely-controlled title somewhere, but I don't want to have to change the PROMPT_COMMAND on every single host I connect to so that it contains the right information.
Is it thus possible to have a part of the window title which is never updated by the host? Preferably it should have the templates as used in KiTTY's window title so a default template string can be stored in the default profile, though just having a static string per saved session would also work for a start.
The text was updated successfully, but these errors were encountered:
I know that you can change the window title using
Window > Behaviour | Window title
, but this field is either static (whenTerminal > Features | Disable remote-controlled window title changing
is checked) or replaced all the time by a remote escape code.The problem is, I want to have full domain names in my window title somewhere and yet keep the remotely-controlled title somewhere, but I don't want to have to change the
PROMPT_COMMAND
on every single host I connect to so that it contains the right information.Is it thus possible to have a part of the window title which is never updated by the host? Preferably it should have the templates as used in KiTTY's window title so a default template string can be stored in the default profile, though just having a static string per saved session would also work for a start.
The text was updated successfully, but these errors were encountered: