Dear visitor, welcome to KDE-Forum.org.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
forcing refresh of fish?
Hi,
I'm using Kate as my primary text editor, and a separate ssh terminal for filesystem operations. I'm noticing that when I perform an operation via ssh, any changes aren't reflected in Kate. I have to shut kate down to cause it to display a folder's contents properly if I modify the folder through ssh.
Does anyone know if there's a way to force a fish resync?
RE: forcing refresh of fish?
Bram Schoenmakers
KDE Netherlands (www.kde.nl)
RE: forcing refresh of fish?
It's not a file, it's a directory. What I'm having trouble with is the resyncing of the directory contents.
I should explain further. 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 I perform 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.
The only thing I've found to fix this so far is restarting Kate.
I was not able to find this possibility. You could submit a bug report at
http://bugs.kde.org .
Bram Schoenmakers
KDE Netherlands (www.kde.nl)
Ok, will do. Wanted to ask around a bit first.
Thx
you should be able to manually hit 'F5' in the file selector view of kate to get it to refresh. Can't remember for certain if this is true, but it seems logical enough.
--Matt
Tried that, and while that did seem to refresh an open file, it did not have an apparent effect on the filesystem browser.
I tried to give focus to the fs browser first (with a mouse click), as well as the filepath entry bar immediately above it, before pressing f5. No dice.
Thanks for the tip, though; it's nice to know about.
I've entered this issure in the kde bug list
here.