Good news!
I found a one-liner patch and now am no longer seeing problems with Konqueror updating file information.
I posted the complete story in the bug report:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=756
I attached the patch to the bug report.
Simply put: the patch works. What a joy to see the file pane update immediately!
The patch should back port to 3.5.13.
Please test!
:) :) :) :)
Darrell
On 04/08/2012 07:16 PM, Darrell Anderson wrote:
Good news!
I found a one-liner patch and now am no longer seeing problems with Konqueror updating file information.
I posted the complete story in the bug report:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=756
I attached the patch to the bug report.
Simply put: the patch works. What a joy to see the file pane update immediately!
The patch should back port to 3.5.13.
Please test!
:) :) :) :)
Darrell
Darrell,
You wrote in the bug:
<quote> For example, in Konqueror select a desired directory, press F4 to open konsole, and then I type something like the following:
diff -urN kdebase kdebase.new > kdebase-new-diff.diff
Konqueror never updates. I have to manually refresh the pane. </quote>
This has always worked in the Arch builds of tde. see:
http://www.3111skyline.com/dl/dt/trinity/ss/konqueror-new-file-updt.jpg
As soon as I create the .diff - it is automatically shown in the konqueror file window. I have kept an eye on this issue even before your post. I authored a bug against kde3 for not refreshing the 'directory' pane with new changes long ago, so I always check.
The only issue I have seen where I have to manually refresh is on remote files systems (eg. fish://) when the directory contents change. Like when I build a package, all packages go in $CHROOT and there is always a $CHROOT/src and $CHROOT/pkg directory under the parent. If I build tdelibs and browse to the tree and view the files, if I then build tdebase (which changes the files in the $CHROOT dir - only then will I have to do a manual refresh.
I'll test the patch, but do you know if it will have any adverse effects where the update appears to be already working?
As soon as I create the .diff - it is automatically shown in the konqueror file window. I have kept an eye on this issue even before your post. I authored a bug against kde3 for not refreshing the 'directory' pane with new changes long ago, so I always check.
The only issue I have seen where I have to manually refresh is on remote files systems (eg. fish://) when the directory contents change. Like when I build a package, all packages go in $CHROOT and there is always a $CHROOT/src and $CHROOT/pkg directory under the parent. If I build tdelibs and browse to the tree and view the files, if I then build tdebase (which changes the files in the $CHROOT dir - only then will I have to do a manual refresh.
I'll test the patch, but do you know if it will have any adverse effects where the update appears to be already working?
I have only been using the patch since yesterday, but I am not noticing anything.
I have seen these problems long since KDE3. I am not the only one because the bug report from which I found the patch was for KDE 3.4.x. This problem has plagued some people for years. As soon as I saw the results in Trinity I back ported the patch to my KDE3 setup as well. For the first time I no longer have to press F5 to refresh the file pane.
I was compiling software yesterday and giggled like a young child when I saw the build log file size continually updating in real time. I never saw that before with KDE3/Trinity.
I don't know why some people have had this problem with Konqueror and some did not.
Darrell