Description of problem:
Up to GNOME 3.6, it is possible to start a new terminal tab/window starting in the same directory as the currently-focused shell.
This is no longer possible - the context menu is no longer present, and launching a new tab using Ctrl-Shift-T or using the menu drops one in one's home directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gnome-terminal
2. Navigate to another directory
3. Start a new tab
New tab's current directory is ~
There should be a way, as before, to have the new tab start in the cwd of the active shell
This should perhaps be reported upstream as well, but I've not had the chance to verify if the bug is also present there
This is not an upstream bug. Citing the gnome-terminal release notes:
To make new tabs opened within Terminal have the same same working
directory as the current tab, it is necessary for the shell running in the
terminal to cooperate. For this, vte installs a bash shell script that you
must use in your bash PS1 prompt. For example, you can put this at the end
of your ~/.bashrc: export PS1='\[$(__vte_ps1)\]'$PS1
Aha, yes, documented for 3.7.0. Any reason for the change from the old behavior?
We should probably coordinate this with Bash and ZSH shell maintainers so that the user experience does not change unexpectedly.
It seems the main reason is that there is a (corner?) case where things can go really wrong:
I am not able to judge whether this was the best fix to apply, but surely we need to document it in release notes and other F19 material.
Please don't forget csh (or tcsh, as it goes).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Since vte 0.34.5 (F19 final has 0.34.6) this is all automatic, so this bug can be closed now.
It should work on bash and zsh.
Re comment 5, there is no [t]csh support, since nobody has requested that upstream. (Since upstream doesn't use [t]csh, a patch would be required.)
Confirmed that it works with bash and zsh, thanks