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

Paul A Norman paul.a.norman at gmail.com
Wed Sep 22 09:17:33 CEST 2010

Thanks for that Stefan,

Just the regular things please -- what OS are you on - version and
revision of TexWorks please.

Is any other application "open" when this happens?

What client are you using for Mercurial please - how do you 'comit'
your work/files?



On 22 September 2010 05:27, Stefan Müller <warrence.stm at gmx.de> wrote:
> Hi list,
> I am experiencing some strange problems when using TeXWorks together with the
> subversion tool Mercurial. Currently, my opinion is that TeXWorks is causing
> the trouble, but I may be wrong.
> I open a .tex-document in TeXWorks, change something, save the file and commit
> the change in Mercurial while TeXWorks is still open. The committed changes
> are stored in separate files, the .tex-file itself is not changed during a
> commit. In about half of the commits something goes wrong in TeXWorks [Why?
> The commit is in Mercurial, TeXWorks should have nothing to do with it...].
> Sometimes TeXWorks just closes itself, which is annoying but not destructive.
> Unfortunately most of the times TeXWorks restores an version of the open file
> which is older than the saved document. If I close TeXWorks at this point no
> harm is done, because this "revert" is not saved [and I am not asked if I want
> to save]. If I don't discover this "revert" in TeXWorks and continue with more
> changes and save, I wreck my .tex-file with old parts of the document.
> This issue sometimes even eats new stuff in my document; when I am not ready to
> commit the new part but commit a different section, the new part may be
> "reverted" to an old version where the new part is not there.
> I hope I clearly outlined the issue. I am in desperate hope that someone can
> give me advice on how to fix this, as I already lost several days of work
> because of this.
> Best regards,
> Stefan.

More information about the texworks mailing list