https://bugs.kde.org/show_bug.cgi?id=387358
nfx...@gmail.com changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=387358
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=387358
Lothar changed:
What|Removed |Added
CC||loh@googlemail.com
--- Comment #7 from Lothar
https://bugs.kde.org/show_bug.cgi?id=387358
Lucas changed:
What|Removed |Added
CC||lche...@gmail.com
--- Comment #6 from Lucas ---
here
https://bugs.kde.org/show_bug.cgi?id=387358
--- Comment #5 from nfx...@gmail.com ---
Can you please consider adding an option to disable this behavior? I already
lost a bunch of changes because of it.
I know other editors reload by default, but that doesn't change that this
behavior is fucking
https://bugs.kde.org/show_bug.cgi?id=387358
--- Comment #4 from nfx...@gmail.com ---
I'm still disliking this very much. Just because a file is git managed, it
doesn't mean you can't lose parts of its contents. For example, this clears the
undo stack. I'd also like more control over this whole
https://bugs.kde.org/show_bug.cgi?id=387358
Nate Graham changed:
What|Removed |Added
CC||pointedst...@zoho.com
--
https://bugs.kde.org/show_bug.cgi?id=387358
--- Comment #3 from nfx...@gmail.com ---
Yes, this is in git repos.
I definitely want the old behavior. There are a lot of cases where you can
actually lose the data forever, and in a few cases the reload notification
saved me. (Cases include e.g. git
https://bugs.kde.org/show_bug.cgi?id=387358
--- Comment #2 from Dominik Haumann ---
How do the files on disk change?
Do you use git pull, and then the files change? Or is it not version
controlled?
I am asking, since for git controlled files, we do not show a reload message
https://bugs.kde.org/show_bug.cgi?id=387358
--- Comment #1 from nfx...@gmail.com ---
PS: as a barely related bug, I've observed that kate _failed_ to reload changes
from disk (after showing the confirmation dialog and instructing it to reload).
This is probably an unrelated bug. Reproduction is
10 matches
Mail list logo