Bug 204733 - kate warn about files modified by a foreign process broken
Summary: kate warn about files modified by a foreign process broken
Status: RESOLVED DUPLICATE of bug 176893
Alias: None
Product: kate
Classification: Applications
Component: kwrite (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 193048 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-22 06:44 UTC by David Rankin
Modified: 2010-05-09 03:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2009-08-22 06:44:44 UTC
Version:            (using KDE 4.3.0)
Installed from:    SuSE RPMs

Kate
Version 3.3.0
Using KDE 4.3.00 (KDE 4.3.0) "release 155"
openSuSE 11.0

The kate "configure kate -> general -> kate warn about files modified by a foreign process" is broken.

This must have just happened. It is really broken. For example if I have a snippet from a log file open and active in kate (meaning it's the document you are looking at) and you modify the file from the command line, kate no longer warns that it has been modified.

For example, the log snippet open in kate (named smberror) needed lines containing the word "MARK" deleted, and since kate can't delete lines, I used the command line:

sed -e '/MARK/d' < smberror > tmpf; cp tmpf smberror ; rm tmpf

I then went back to kate expecting the normal file modification message and got nothing. I switched to another doc and then back to the file "smberror" and still no warning.

It wasn't until I manually said "Reload File" that the changes were brought in.

So I tested again with:

echo "testline" >> smberror

Still nothing -- something broke in the last update...
Comment 1 David Rankin 2009-08-22 08:07:20 UTC
Another new problem with this is that if you change file permissions on the file open in kate from the command line, then save in kate, the file permissions are changed back to the file permissions when the file was opened in kate. Here I'm working in kate on host "alchemy" editing a file via sftp on host "supersff". The file being edited was a script. I checked the file permissions from the command line, changed them to 0754, then saved the file with kate and the permission were changed back to 0644. This should never happen.

00:45 supersff:~/scripts/file> l
total 28
-rw-r--r-- 1 david david  564 2009-08-22 01:00 fdup-archpkg

01:00 supersff:~/scripts/file> chmod 0754 fdup-archpkg
01:00 supersff:~/scripts/file> l
total 28
-rwxr-xr-- 1 david david  564 2009-08-22 01:00 fdup-archpkg

<the save in kate occurred here>

01:00 supersff:~/scripts/file> l
total 28
-rw-r--r-- 1 david david  571 2009-08-22 01:00 fdup-archpkg

    kate never warned that the permissions had been changed (you used to be able to configure whether it would for permissions in kde3). But, regardless, it changed the permissions back after I changed them from the command line.
Comment 2 Joseph Wenninger 2009-09-20 22:11:28 UTC
currently kate just shows an icon in the document list. In the general settings notification can be enabled, but the dialog only appears if the main window loses and regains focus. I'm working on displaying the dialog, even if the main window does not lose focus
Comment 3 Cade Robinson 2010-03-25 15:03:06 UTC
This still happens in 
Version 3.4.1
Using KDE Development Platform 4.4.1 (KDE 4.4.1)

I edit files over fish:// a lot but kate doen't pick up if someone vi's the file on the remote server.
I tried to leave focus and come back but it still didn't pop up a warning.
Comment 4 Dominik Haumann 2010-05-09 03:18:13 UTC
*** Bug 193048 has been marked as a duplicate of this bug. ***
Comment 5 Dominik Haumann 2010-05-09 03:19:19 UTC

*** This bug has been marked as a duplicate of bug 176893 ***