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 767313 - Shouldn't shortcut uri-changed signal
Shouldn't shortcut uri-changed signal
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
git master
Other Linux
: Normal minor
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-06-07 05:56 UTC by Egmont Koblinger
Modified: 2021-06-10 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2016-06-07 05:56:03 UTC 
If multiple current-directory-uri-changed (or window-title-changed or whatever similar) events occur almost immediately after each other, only a single signal is sent. As such, the container application has no chance to see the ephemeral intermediate value.

As reported in bug 709055, when opening a new tab the last seen local directory should be used, that is, if current-directory belongs to a remote host, it should be ignored.

One possible approach is to filter out remote hosts on VTE level (and just pretend those OSC 7's were not seen at all), but this would make it impossible to use OSC 7 for the purpose of profile change (https://github.com/gnunn1/terminix/issues/135#issuecomment-224130095) and also I don't think that's the right design.

But this means that there might be two OSC 7's right after each other, the first belonging to a local directory, the second belonging to a remote one. In order for being able to open a new tab in the last seen local directory, a signal should be sent for that one too.
Comment 1 GNOME Infrastructure Team 2021-06-10 15:14:09 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vte/-/issues/2315.