Re: [racket-dev] overwrite

2011-02-27 Thread Robby Findler
Yes, that's it. Also, put something into the after-save-file-method: diff --git a/collects/framework/private/editor.rkt b/collects/framework/private/editor.rkt index 0c8981b..cb5504a 100644 --- a/collects/framework/private/editor.rkt +++ b/collects/framework/private/editor.rkt @@ -190,7 +190,8 @@

Re: [racket-dev] overwrite

2011-02-27 Thread John Clements
On Feb 27, 2011, at 11:42 AM, Robby Findler wrote: Yes, that's it. Also, put something into the after-save-file-method: diff --git a/collects/framework/private/editor.rkt b/collects/framework/private/editor.rkt index 0c8981b..cb5504a 100644 --- a/collects/framework/private/editor.rkt +++

Re: [racket-dev] overwrite

2011-02-27 Thread Eric Hanchrow
Looking at this code, I'm betting on Neil's suggestion of NTP, though I realize that the mechanism isn't obvious... perhaps the OS adjusts the save times of recently-saved files? I haven't followed this discussion closely, nor looked at the relevant code. However :) From what I know about

Re: [racket-dev] overwrite

2011-02-27 Thread Eli Barzilay
Two hours ago, John Clements wrote: Add'l data point: I tried messing up the clock manually, by turning off NTP, but I was unable to duplicate the bug this way. NTP is unlikely to be the problem, since the times are saved on the filesystem, independently of the system time (or clock). And