https://bugs.kde.org/show_bug.cgi?id=416647
--- Comment #9 from Thomas Fischer <fisc...@unix-ag.uni-kl.de> --- Some comments on your comments > kbibtex.parts: watchableFilename is Empty Debug output from the monitor looking for other programs changing files currently open in KBibTeX. The message is irrelevant for remote files (no monitoring there). > kbibtex.io: Don't know how to encode Unicode char "0x0301" > kbibtex.io: Don't know how to encode Unicode char "0x2010" There are thousands of Unicode characters for which no mapping to a LaTeX command is known to KBibTeX; you just encountered two of those. If you provide me with an example file containing BibTeX data with those characters, I can look for a fix, but it is not urgent and not relevant for this bug here. > Each time I try to "Save", I get (almost immediately) these four lines on > output: > > kbibtex.parts: watchableFilename is Empty > kbibtex.io: Don't know how to encode Unicode char "0x0301" > kbibtex.io: Don't know how to encode Unicode char "0x2010" > kbibtex.parts: watchableFilename is Empty None of the additional debug output I added in my recent changes got printed. It looks like the run-kbibtex.sh script didn't have all debug settings enabled. I updated this script now, so please fetch the most recent version of this script kbibtex-related.git and run everything again. Sorry for the hassle ... > qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14661, > resource id: 55074827, major code: 40 (TranslateCoords), minor code: 0 That is due to X being a complex, broken protocol (but still alive). > Let me also explain the results from an additional little test: this time I > modified the remote file, while keeping kbibtex open (I know, a sensible > user should never do this), not 'directly' (using a konsole on the server) > but locally (using Kate); this is the summary (scheme) of the file update > history: > > #1 original remote file opened locally both in kbibtex and kate > #2 version modified internally in kbibtex, but cannot be updated into remote > directory > #3, #4, #5 subsequently modified versions in Kate, successfully updated each > time in the remote directory > > At this point, the original (#1) file only 'lives' as a temporary file > (somewhere). If now I try a "Save" in bibtex, #1 reappears again in the > remote directory (it overwrites the newer version #5, previosly saved by > Kate). 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? Interesting behaviour ... -- You are receiving this mail because: You are watching all bug changes.
