Bug 310314 - Opening two fish:// files with same name but different URL make the full path in window title to fail
Summary: Opening two fish:// files with same name but different URL make the full path...
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-19 09:31 UTC by Iñaki Baz Castillo
Modified: 2017-06-13 17:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iñaki Baz Castillo 2012-11-19 09:31:55 UTC
When opening with fish:// two remote files with same name, the file full path in the window title displays wrong path (randomly between both paths).

Reproducible: Always

Steps to Reproduce:
1. Open two fish:// files with same name (i.e:  fish://myserver-1.org/tmp/test.txt and fish://myserver-2.org/tmp/test.txt).

2. Select any of them in the file left bar (directory search). You could see "fish://myserver-1.org/tmp/test.txt" in the window title.

3. Then select the other file. You would see the same "fish://myserver-1.org/tmp/test.txt" in the window title.

4. Press F5 to reload any of them. Now you may be "fish://myserver-2.org/tmp/test.txt" in the window title regardless you select any of both files.
Actual Results:  
The full path in the window title shows a random path regardless which file is selected.

Expected Results:  
The full path should be the appropriate one.

It seems that Kate gets confused when two files share same directories path and name (regardless they are different remote files).
Comment 1 Darren Lissimore 2017-06-03 07:22:49 UTC
Just tried reproducing this one following the steps described and can't reproduce.
Used kate from git build from commit e4f135bddb2f894f0f776b7f75384e8ef3cb661a.

Think that bug is not an issue anymore. Would recommend closing.
Comment 2 Christoph Feck 2017-06-13 17:44:11 UTC
Thanks for the update; closing. The fix might be a consequence of the KF5 port.