After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 564510 - New terminals/tabs open at canonical (not necessarily same) path of current terminal
New terminals/tabs open at canonical (not necessarily same) path of current t...
Status: RESOLVED DUPLICATE of bug 502146
Product: gnome-terminal
Classification: Core
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-14 18:45 UTC by Daniel Holbert
Modified: 2008-12-14 18:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Daniel Holbert 2008-12-14 18:45:08 UTC
Please describe the problem:
When I'm in a symlink-directory and I open a new terminal or tab, it opens at the *canonical* path of my current directory.  If my current directory is a symlink (or has a symlink as an ancestor), then this is a *different path* (which, granted, points to the same location).

Steps to reproduce:
1. Open gnome-terminal in your home directory.
2. Create a symlinked directory:        ln -s /tmp mytmp
3. Step into the symlinked directory:   cd mytmp
4. Ctrl-Shift-T to open a new tab


Actual results:
The new tab opens at /tmp

Expected results:
The new tab should open at ~/mytmp (matching the old tab)

Does this happen every time?
yes

Other information:
This is particularly annoying for me because I use symlinks to obscure long directories. e.g. I have a path like ...
   /scratch/work/builds/trunk_builds/trunk_checkout.long_datestamp_goes_here/
... which I symlink as ...
   ~/builds/latest-trunk/
... and whenever I open a new tab from my short symlink directory, it opens using the really-long-and-ugly canonical directory.
Comment 1 Christian Persch 2008-12-14 18:59:10 UTC
It's discussed in bug 502146 ("issue C") why it's this way.

*** This bug has been marked as a duplicate of 502146 ***