Bug 338819 - Kate does not auto-select the only modified file on disk
Summary: Kate does not auto-select the only modified file on disk
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: Git
Platform: Chakra Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-05 07:54 UTC by Martin
Modified: 2016-06-20 06:14 UTC (History)
1 user (show)

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


Attachments
Example of the grey »View difference« button with one changed file (51.03 KB, image/png)
2014-09-05 07:55 UTC, Martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2014-09-05 07:54:02 UTC
When one or multiple files which are opened in kate are modified kate opens a window which lets you reload the files, discard changes or view differences. When only one file has been modified kate should automatically select the file so that the option »View difference« is immediately clickable.
I have Version 3.14 (which has not been added so far to the version list).

Reproducible: Always
Comment 1 Martin 2014-09-05 07:55:53 UTC
Created attachment 88572 [details]
Example of the grey »View difference« button with one changed file
Comment 2 Buovjaga 2016-06-19 13:19:10 UTC
Now it behaves like this: when you have a couple of files open and only one is modified through some other editor, Kate opens the dialog when you click on the tab of the modified file. View difference is immediately clickable.

Martin: are you happy with this situation, or do you think it should pop up the dialog immediately when focusing on Kate and not only when focusing on the tab of the modified file?
Comment 3 Martin 2016-06-19 19:52:33 UTC
I think this is a very good solution: Kate is not intrusive and writing to another file does not get interrupted. Otherwise, e.g. log files would be really annoying. Can you add the version that contains the new behaviour?
Comment 4 Buovjaga 2016-06-20 06:14:17 UTC
Oops, sorry for not mentioning the version: it is 16.04.2
I'll set the status to WFM as we don't know the history of the change :)