On Tue, Mar 8, 2011 at 3:59 PM, John Clements wrote:
>
> On Fri, Mar 4, 2011 at 3:24 PM, Jakub Piotr Cłapa
> 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 turning
off NTP,
On Fri, Mar 4, 2011 at 3:24 PM, Jakub Piotr Cłapa 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 turning
>>> off NTP, but I was unable to duplicate the bug this way.
>>>
>>
>> NTP is un
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, independently
Is this happening on network-mounted drives?
One strange thing I've run into in the past is that on SMB-mounted
filesystems, the timestamp is rounded off to a multiple of 2 seconds.
It seems like that could cause this problem.
rsync has a --modify-window parameter to accommodate this.
e.g. see h
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
> 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 abo
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
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 10:08 AM, John Clements wrote:
>
> 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?
One other note; if it's NTP, it would probably happen on
On Feb 26, 2011, at 9:26 AM, Kathy Gray wrote:
> Same answers.
> -Kathy
+1
I've seen this for ~ 6 months; I believe I've reported it before, but never
followed up on it adequately. At least one of my students has also seen it.
To add a few details: It usually happens on a "run", asking if I w
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 wrote:
> Dunno whether this helps...
>
> I haven't looked at the pertinent Racket code, but errors like this often
> happen in Unix a
Dunno whether this helps...
I haven't looked at the pertinent Racket code, but errors like this
often happen in Unix applications because the mtime of the file is in
the future relative to the current time clock. Less commonly, because
the mtime changed since the file was read by the app or s
Looking at the code, I don't see anything suspicious (assuming that
after-save-file and file-or-directory-modify-seconds work properly,
that is).
If you find a way to make it happen (even if it only works 1 in 10
tries or something), that would help.
Or if you had the energy to instrument the aft
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
>
>
>> - hitti
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 save right *after* run
no
>
> when you get this message?
>
> Robby
>
>
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 wrote:
> I get this a lot, using just the
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
wrote:
>
> Well i
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 contr
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.
>
> -Kat
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
On 26 Feb 2011, at 4:36:37, Matthias Felleisen wrote:
>
> The files I have been editing this
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
It's from git touching the files and giving them a new timestamp. It
probably didn't really change.
Jay
2011/2/26 Matthias Felleisen :
>
> When I use drracket, I frequently get a warning that my file has been
> modified on disk and the question of whether I want to save the file or
> revert. Is
When I use drracket, I frequently get a warning that my file has been modified
on disk and the question of whether I want to save the file or revert. Is
anyone else suffering from this problem?
_
For list-related administrative tasks:
http://l
23 matches
Mail list logo
