On Tue, Mar 8, 2011 at 3:59 PM, John Clements cleme...@brinckerhoff.org wrote:
On Fri, Mar 4, 2011 at 3:24 PM, Jakub Piotr Cłapa jpc...@zenburn.net
wrote:
On 27.02.11 23:33, Eli Barzilay wrote:
Two hours ago, John Clements wrote:
Add'l data point: I tried messing up the clock manually, by
On 27.02.11 23:33, Eli Barzilay wrote:
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,
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 @@
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
+++
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
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
The files I have been editing this morning are not under Git control.
(And yes, I have on one occasion checked the file via Emacs and didn't
see any difference.)
On Feb 26, 2011, at 11:35 AM, Jay McCarthy wrote:
It's from git touching the files and giving them a new timestamp. It
probably
I confirm the check syntax observation.
On Feb 26, 2011, at 11:39 AM, Kathy Gray wrote:
I also see this quite frequently (for files not under Git control). I was
thinking at one point it might be related to when I run check syntax, but I
haven't confirmed a repeatable pattern.
-Kathy
Well it just occurred for a file under Git but WITHOUT check syntax.
On Feb 26, 2011, at 11:48 AM, Matthias Felleisen wrote:
I confirm the check syntax observation.
On Feb 26, 2011, at 11:39 AM, Kathy Gray wrote:
I also see this quite frequently (for files not under Git control). I
I get this a lot, using just the binary installer version downloaded
from racket-lang.org. And it happens even when I'm not using
check-syntax, though it might happen more frequently when I do use
check-syntax; hard to tell.
On Sat, Feb 26, 2011 at 12:05 PM, Matthias Felleisen
Are any of you, by any chance:
- using a teaching language (via the language menu, not #lang
2htdp/bsl or similar)
- hitting run and then save right *after* run
when you get this message?
Robby
On Sat, Feb 26, 2011 at 11:10 AM, Nadeem Abdul Hamid nad...@acm.org wrote:
I get this a lot,
Same answers.
-Kathy
On 26 Feb 2011, at 5:23:56, Matthias Felleisen wrote:
On Feb 26, 2011, at 12:12 PM, Robby Findler wrote:
Are any of you, by any chance:
- using a teaching language (via the language menu, not #lang
2htdp/bsl or similar)
#lang racket
- hitting run and then
The code compares the date of the file when it was last saved to the
date of the file when run is clicked.
Robby
On Sat, Feb 26, 2011 at 12:50 PM, Neil Van Dyke n...@neilvandyke.org wrote:
Dunno whether this helps...
I haven't looked at the pertinent Racket code, but errors like this often
13 matches
Mail list logo
