Re: something.tex changed on disk; really edit the buffer?

[agjf . tucker]

Yes, to clarify, this is on my local disk.  Noone else has access.

I looked up auto-revert-mode, thanks for the suggestion Alexander, however from 
the description it's not at all the desired behaviour...

On Tuesday, 7 October 2014 08:40:19 UTC+1, sokoba...@gmail.com  wrote:
> Le lundi 6 octobre 2014 17:01:22 UTC+2, agjf....@gmail.com a écrit :
> 
> > Hi!
> 
> > 
> 
> > 
> 
> > 
> 
> > I am using Aquamacs with AUCTeX and Skim to edit and view LaTeX documents.  
> > It used to work just fine but when I upgraded to version 3.0a (based on 
> > Emacs 24), I started to get these sorts of messages.
> 
> > 
> 
> > 
> 
> > 
> 
> > Specifically, I will have run LaTeX using the button at the top.  Then I 
> > will try to start editing again.
> 
> > 
> 
> > 
> 
> > 
> 
> > At the bottom of the frame I will get my first message, "Something.tex 
> > changed on disk; really edit the buffer? (y,n,r or C-h)"  I press "y" to 
> > keep editing.
> 
> > 
> 
> > 
> 
> > 
> 
> > Then when I go to run LaTeX again, a dialog box pops up saying, 
> > "something.tex has changed since visited or saved.  Save anyway?"  I click 
> > on the "Yes" button to run LaTeX.
> 
> > 
> 
> > 
> 
> > 
> 
> > Immediately I will get at the bottom of the frame, "something.tex changed 
> > on disk; really edit the buffer? (y,n,r or C-h)".  I press "y".
> 
> > 
> 
> > 
> 
> > 
> 
> > And then it's fine again for a little while!
> 
> > 
> 
> > 
> 
> > 
> 
> > There is a thread about this already on the Aquamacs group: 
> > https://groups.google.com/forum/#!topic/aquamacs-devel/yX-kkfJTNlU.
> 
> > 
> 
> > 
> 
> > 
> 
> > There was some suggestion that it might be related to use of a file hosting 
> > service like Dropbox, and it's true I used to have Dropbox installed.  But 
> > I uninstalled it some time ago (because I thought that might resolve this 
> > problem).
> 
> > 
> 
> > 
> 
> > 
> 
> > David Reitter (author of Aquamacs) says it is not a problem of his making 
> > and that I might have better luck asking here.
> 
> > 
> 
> > 
> 
> > 
> 
> > Thanks, Alistair.
> 
> 
> 
> I happened to see some strange behavior (I can't remember if it's the same) 
> when the file was hosted on a server with a clock out of sync (the file was 
> considered newer than the current time on the machine running emacs).
> 
> But, if you use only one macintosh with a local hard drive, this can not be 
> the correct explanation.