Bug 124447 - Filesystem browser does not refresh properly using fish:// protocol
Summary: Filesystem browser does not refresh properly using fish:// protocol
Status: RESOLVED INTENTIONAL
Alias: None
Product: kio
Classification: Unmaintained
Component: fish (show other bugs)
Version: 0.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Walter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-28 22:01 UTC by Aron Beal
Modified: 2006-11-04 23:48 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Beal 2006-03-28 22:01:00 UTC
Version:           2.4.1 (using KDE KDE 3.4.3)
Installed from:    Ubuntu Packages
Compiler:          gcc version 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9) 
OS:                Linux

Note: this bug is somewhat related to #72696 and #39226

While using Kate, when using the left hand filesystem browsing tab, and viewing the contents of a remote directory via the fish:// protocol, the directory contents do not reflect external changes properly. That is, when performing an operation ouside of kate via a normal terminal ssh to the same directory, that operation does not show up in the kate filesystem navigation.

Restarting Kate will cause contents to display correctly.

Steps to reproduce (for me):
1) Navigate to any directory on a remote machine using the fish:// protocol in the Kate filesystem browser
2) Open a separate terminal, and ssh to the same machine.  Navigate to the same directory.
3) Either touch a file into existence, or copy a file into that directory that wasn't there before, using the separate terminal to do so.
4) Kate does not display the new file, but it is confirmed as being present using the terminal instance.
Comment 1 Anders Lund 2006-03-28 22:14:33 UTC
If you use this a lot, you could add a refresh button to the file browser's toolbar.
Comment 2 Aron Beal 2006-03-29 00:18:38 UTC
That would certainly help me right now.
 
 Where is this done?  Settings->Configure Toolbars... allows me to edit the toolbars Kate and KatePartView.  Neither of these seems to be the toolbar associated with the filesystem browser, however.
 
 ~Aron

Anders Lund <anders@alweb.dk> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=124447         
anders alweb dk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|kwrite-devel kde org        |trouble garni ch
          Component|general                     |fish
            Product|kate                        |kio
            Version|2.4.1                       |0.1



------- Additional Comments From anders alweb dk  2006-03-28 22:14 -------
If you use this a lot, you could add a refresh button to the file browser's toolbar.


		
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2
Comment 3 Aron Beal 2006-03-29 00:21:24 UTC
Ugh. Sorry about the mess.
Comment 4 Martin Koller 2006-11-04 14:43:15 UTC
Can confirm with KDE-3.5.5; don't know if this is possible at all (I mean a dirlister for a remote URL)
Comment 5 Martin Koller 2006-11-04 23:48:42 UTC
Info from David Faure:
> I ask myself if it is possible at all to watch a remote URL for changes ?

No, it isn't. I don't think fish:// even provides any way to implement it... well, other
than polling, see below.

The KIO framework has support for notification of changes to remote file systems:
KDirNotify is a dcop/dbus interface where changes are announced; this is called by
konqueror, but this doesn't help you for changes made by others of course.

Something would have to list the fish directory regularly and compare the output,
I don't see another way. And actually KDirLister does exactly that (listing and comparing)
when it is notified of a change... so this is equivalent to -assuming- that there is a change,
regularly, in KDirLister. This would work, but it would result in a rather large
utilisation of the network and the server -- I'm not sure this is a good idea.


=> WONTFIX