https://bugs.kde.org/show_bug.cgi?id=416647
--- Comment #11 from Joan <joan.herr...@urv.cat> --- (In reply to Thomas Fischer from comment #10) > Can you please test the lastest code? Also, is my summary from comment 9 > correct? > > (In reply to Thomas Fischer from comment #9) > > If I understand it correctly, if you in KBibTeX: > > 1. Open a remote file > > 2. Modify the file > > 3. Save it to the same remote location under same name ... > > ... the file saved in step three is not containing the modifications made in > > step 2 but is still the old one as it was in step 1? > > And by concurrently modifying the remote file in Kate, you know that KBibTeX > > actually writes something to the remote location in step 3? I can confirm your summary is correct. I'm working now in a different hardware, same system+DEnv (KDE/Plasma 5.18.3). I have downloaded, compiled and executed kbibtex from git as explained in #2. I get the same previous anomalous behavior when trying to save the modified .bib file to a remote system via sftp. I have however spotted two small differences with respect to the previous tests: a) Now both the "Save" and the "Save As" commands fail to replace the original (remote) file by the modified one. However, the "Save Copy As" command works, it saves the modified version of the file into the remote system (as a new file, different name). b) When performing either the "Save" or the "Save As" operations described above, I get now a system notification of: "Moving (Finished)", followed by the corresponding sftp command (in correct syntax, I would say). However, when I perform the "Save Copy As", I get no such a notification. That is, somehow the two first commands (that fail to replace the file) trigger a file-moving operation in the KDE environment whereas the latter command (that is working as supposed) does not. -- You are receiving this mail because: You are watching all bug changes.
