Bug 359691 - "Warn about files modified by foreign processes" no longer working
Summary: "Warn about files modified by foreign processes" no longer working
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: 3.14.2
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-23 03:09 UTC by Red Squirrel
Modified: 2016-08-29 00:26 UTC (History)
2 users (show)

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 Red Squirrel 2016-02-23 03:09:18 UTC
Using latest kate version from Mint 17.1 KDE (3.14.2) and noticed that recently, there is no longer a warning when a file has been modified by another process. 

Reproducible: Always

Steps to Reproduce:
1. Open a file in Kate
2. Modify that file using another program, such as vim
3. Switch back to Kate Window and click on the opened file - you should be prompted with a warning asking if you want to reload the file because it changed

Actual Results:  
Nothing.  It is now possible to hit save and overwrite any changes that were made in the other program. (ex: coding remotely then coming back home to continue coding)

Expected Results:  
There should be a prompt saying that the file changed, asking what to do with it

All files are stored via NFS.  It's worked before. 

On a side note, the "Disable swap files syncing" option also does not work and can make using KATE with NFS files unbearable if there is a backup job or other latency on the file server.  I am wondering if there is a bigger issue here, perhaps none of the options are actually registering.
Comment 1 Buovjaga 2016-07-01 11:00:47 UTC
Do you mean the problem only appears with NFS storage?
Comment 2 Red Squirrel 2016-08-29 00:26:21 UTC
I believed it was only doing it with NFS but I just tested again to confirm and it seems to be working now. It's possible it was fixed since the time I submitted the report.  I'll close the report.  

The disable swap file syncing issue still exists though, but I will open a new bug report for that.