desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #74524
[Bug 1132700] Re: gnome-terminal >= 3.7 requires sourcing of vte.sh login script
One more thing to consider with the "fallback" approach:
If you do this, users who've manually set PROMPT_COMMAND will remain
with the old method of figuring out the cwd, including all its bugs and
limitations (not remembering symlink components, not working after sudo,
etc.) They would probably live on with these compromises, unaware that
there is a better solution.
If you don't do the fallback, those users will be pushed to switch to
the new, better solution with all its advantages.
Your call. I would personally probably do the fallback if /etc/skel
ever shipped a PROMPT_COMMAND for the sake of those users, but not ship
the fallback otherwise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.sh login script
Status in GNOME Terminal:
New
Status in “gnome-terminal” package in Ubuntu:
Triaged
Bug description:
As of gnome-terminal 3.7.0, it is required to add the following to
PS1 to get the usual behaviour where a new terminal opens with the
current working directory of the terminal you activated it from.
export PS1='\[$(__vte_ps1)\]'$PS1
gnome-terminal devs suggest to put this in .bashrc, however since this
basically causes a regression, it would make sense to deal with it at
a distro level and perhaps include it in the system bash scripts or
similar.
The actual change was made in libvte so this may potentially affect
any application that uses that library.
As a side note: __vte_ps1() is provided by /etc/profile.d/vte.sh,
which is installed by libvte, however atleast on my system this script
is not getting sourced at login for some reason.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1132700/+subscriptions