Seems something is doing an s/$HOME/~/ somewhere.  I can kind of understand why that might be considered a feature, but perhaps a well placed beginning-of-string anchor could add just that final touch of perfection...

(Yes, I have /home symlinked to /var/home; that is not the WTF.  And yes, it does the same whenever $HOME occurs as a substring of the path.)

(Actually, the bug is probably in bash, not in konsole.  Or maybe it's working as designed; the documentation does say: "\w The current working directory, with $HOME abbreviated with a tilde.")

The bug is probably in your bash startup files (incl: ~/.bash_profile (or ~/.profile), ~/.bashrc, /etc/profile, /etc/bash/bashrc, or anything sourced by one of those). Basically, it's doing something similar to this:

PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\007"'

But it needs to be:

PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}\007"

(The leading # makes it work like ^ in regex: anchors at the beginning.)

I have seen bashrc that have a variant specifically for screen (eg to use screen's title commands instead of xterm), so you may have to change this more than once. (Why they couldn't just parse termcap/terminfo? I dunno.)

Note that PS1 isn't affected by this as can be seen in your screenshot.

(Edit: and yes, this would be WTF worthy if it's the distro's bashrcs that are doing this. In fact, I just checked and my Gentoo system bashrc has this bug so others may too. You'd think distro maintainers would actually READ bash's manpage. And if turns out the bashrc came from upstream (==bash), that would double the WTF-ness :) .

(Edit: and yes, this would be WTF worthy if it's the distro's bashrcs that are doing this. In fact, I just checked and my Gentoo system bashrc has this bug so others may too.

MasterPlanSoftware: