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
Originally posted by piki January 4, 2025
The PS1= variable in the bash integration for the title bar could use \w rather than $PWD to indicate the working directory.
The effect is to replace any leading instance of $HOME with a tilde, so /Users/patrick/code becomes ~/code. It also respects $PROMPT_DIRTRIM, if any. It looks cleaner to me, especially if there are multiple tabs open.
The "set title" command is purely informational, so $PROMPT_DIRTRIM's abbreviation behavior shouldn't cause any functional issues. (We can rely on \e]7;kitty-shell-cwd://.. to report the full current working directory.)
I think it's possible some people might like to further customize their title, but they can do that in through their own shell configuration and disable our "title" shell integration feature.
The text was updated successfully, but these errors were encountered:
Discussed in #4601
Originally posted by piki January 4, 2025
The
PS1=
variable in the bash integration for the title bar could use\w
rather than$PWD
to indicate the working directory.The effect is to replace any leading instance of
$HOME
with a tilde, so/Users/patrick/code
becomes~/code
. It also respects$PROMPT_DIRTRIM
, if any. It looks cleaner to me, especially if there are multiple tabs open.Implemented in this branch.
From @jparise:
This sounds like a good improvement to me, and it looks like we do something similar in the zsh shell integration:
ghostty/src/shell-integration/zsh/ghostty-integration
Line 200 in f4a9b65
The "set title" command is purely informational, so
$PROMPT_DIRTRIM
's abbreviation behavior shouldn't cause any functional issues. (We can rely on\e]7;kitty-shell-cwd://..
to report the full current working directory.)I think it's possible some people might like to further customize their title, but they can do that in through their own shell configuration and disable our "title" shell integration feature.
The text was updated successfully, but these errors were encountered: