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

[agjf . tucker]

Thanks!  These are the results I get

M-: (visited-file-modtime)
(21568 8785 0 0)

M-: (file-attributes something.tex)
(nil 1 501 20 (21568 8805 0 0) (21568 8811 0 0) (21568 8811 0 0) ... )

I guess this means that it's Emacs' file-writing mechanism that is broken?  Or 
OSX itself? (seems less likely...)

Ali



On Thursday, 9 October 2014 19:57:42 UTC+1, Barry Margolin  wrote:
...
> 
> 
> 
> > I have searched the archives, where I found this advice to someone 
> > suffering 
> 
> > a similar problem:
> 
> > 
> 
> > "To find out what's going on, invoke the function visited-file-modtime from 
> 
> > the buffer of the offending file, and compare the result it returns with 
> > the 
> 
> > time stamp for that file returned by file-attributes."
> 
> > 
> 
> > I have tried running these functions with M-x but I get [No Match].  Any 
> 
> > ideas?
> 
> 
> 
> These are Lisp functions, not interactive commands. Run them with M-:
> 
> 
> 
> M-: (visited-file-modtime)
> 
> M-: (file-attributes buffer-file-name)
> 
> 
> 
> -- 
> 
...