[texworks] external read-access causes TeXWorks to revert open file to old version

Stefan Löffler st.loeffler at gmail.com
Tue Nov 2 19:16:46 CET 2010


Am 2010-11-02 16:51, schrieb Stefan Müller:
> I asked at the TortoiseHG list and someone pointed out what's going
> on. TortoiseHG enables me to select "hunks of changes", i.e. I can say
> I want to commit changes 3, 4, 6 and keep changes 1, 2, 5 uncommitted
> for the next commit (or whatever). To handle these types of commits
> TortoiseHG has to: backup all changes locally, revert the file, apply
> the changes for commit, commit, apply the other changes. That's why
> the file changes.

OK, that sounds like it confirms my theory :).

> So the file is changed 3 times if I understood this right. Is it
> possible for TW to detect every change of the files and not just the
> first? So that in the end the current version is restored? It seems to
> me that this should be possible without doing stuff like "wait 2
> seconds before reloading after changes".

Waiting is definitely not a good option. Imagine some user with a slower
PC suddenly experiencing the same problem because we didn't wait long
enough ;).
Could you try the attached patch? It should reload files multiple times
if they change in-between.
To apply patches in *nix run the following command from your
texworks-read-only directory:
patch -p0 < issue-426_reload-file-until-up-to-date.diff
and then rebuild Tw using make.


PS: I've opened a new issue on Google Code
(http://code.google.com/p/texworks/issues/detail?id=426), basically for
when the patch works.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: issue-426_reload-file-until-up-to-date.diff
Type: text/x-patch
Size: 1199 bytes
Desc: not available
URL: <http://tug.org/pipermail/texworks/attachments/20101102/464aa7c6/attachment.bin>

More information about the texworks mailing list