[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram

[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0

[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 jMdZ changed: What|Removed |Added CC||mauro.da...@gmail.com -- You are receiving this mail

[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 --- Comment #3 from Mykola Krachkovsky --- More thoughts about more complex and nice solution as I see it. It could be done at moment of recalculation of fold positions or later. If we do check later we have something like two

[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 --- Comment #2 from Mykola Krachkovsky --- >From my perspective simplest solution is to unfold all folds when external update is coming. That will fix at least while Kate is running. As we have no support to fold/unfold all

[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update

https://bugs.kde.org/show_bug.cgi?id=384459 --- Comment #1 from Christoph Feck --- I doubt it is possible to fix this. Kate would need to keep a copy of the original file and do a diff with the updated file to see if any of the folding markers still apply to the updated file. --