Re: [racket-users] Re: truly stand-alone Windows ".exe"s

On Tuesday, March 27, 2018 at 9:17:49 PM UTC+8, Matthew Flatt wrote: > > I should have bumped the version number when adding `--embed-dlls`, but > I didn't. So, even though it's still version 6.90.0.23, `--embed-dlls` > is in snapshots starting with the ones built on March 26. > I tried the

Re: [racket-users] Profiling places

On 27/03/18 17:18, Vincent St-Amour wrote: > On Tue, 27 Mar 2018 07:55:08 -0500, > 'Paulo Matos' via Racket Users wrote: >> >> I was trying to confirm my suspicion that profile needs to be manually >> setup in each place for profiling. > > Right. Each place has its own separate runtime, and the

[racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

Quick update - doing a fresh install of Racket solved the problem on my machine, an interesting case nevertheless. On Wednesday, March 28, 2018 at 1:07:14 AM UTC+2, Greg Trzeciak wrote: > > Forgot to mention - my setup is: Racket 6.12 on Windows 10... could be > some recent Windows update? >

Re: [racket-users] Profiling places

On 28/03/18 10:23, 'Paulo Matos' via Racket Users wrote: > True, I can confirm that. I will open an issue on this. Done #2019. https://github.com/racket/racket/issues/2019 -- Paulo Matos -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To

Re: [racket-users] Re: truly stand-alone Windows ".exe"s

At Wed, 28 Mar 2018 00:54:01 -0700 (PDT), Alex Harsanyi wrote: > > > On Tuesday, March 27, 2018 at 9:17:49 PM UTC+8, Matthew Flatt wrote: > > > > I should have bumped the version number when adding `--embed-dlls`, but > > I didn't. So, even though it's still version 6.90.0.23, `--embed-dlls` >

Re: [racket-users] Behavior of nested ellipses

> On Mar 27, 2018, at 11:58 PM, Justin Pombrio wrote: > > Matthias: the algorithm I was thinking of is the Macro-by-Example algorithm > that Ryan pointed out, which is neither of yours. Decompose the environment > at the outer ellipsis. I take back my claim that it's

Re: [racket-users] error during prompt calculation: path->string: contract violation

The correct link seems to be https://github.com/racket/racket/issues/2023 (no final 0) -Philip On Wed, Mar 28, 2018 at 3:23 PM, Kieron Hardy wrote: > > An error report on the `enter!` problem would be welcome. >> >> > >> > D:\>racket >> > Welcome to Racket v6.12. >> > >

Re: [racket-users] Resubmitting PRs after build problems

If you make another commit to that PR, then it will rebuild. I'm not sure how to do that from the web interface though. Sam On Wed, Mar 28, 2018, 11:32 AM Kieron Hardy wrote: > Hi all, > > I have noticed that some recent PRs have failed the Travis CI build step >

[racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

I was too quick with the success update - although I was able to install some packages that were failing before, the problem is not resolved for other packages - I have just tested "syndicate" package - exactly the same error. In the offline conversation with Kieran Hardy we briefly discussed

[racket-users] Embedding image files in a executable file

Hi, everyone. I'm making a simple game. I want to embed some image files in ONLY-ONE executable file. I need it for a simple distribution. Do you think that it displays the error message "no image files" when you execute the application? For example, [image.rkt] #lang racket (provide

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

Before I disappear for today - some additional observations + current hack if anyone has the same problem: * folders have correct timestamps * dependencies downloaded in the same run can have their timestamp even +2h into the future. * install directly from git has the same problem -> "raco pkg

[racket-users] (eighth RacketCon) is St. Louis in September 2018

Prepare yourselves! (eighth RacketCon) is St. Louis in September 2018! http://con.racket-lang.org co-located with ICFP and Strange Loop! -- At this point, you can book your hotel room (get them fast!) and let me know what you plan on presenting! Jay -- -=[ Jay McCarthy

Re: [racket-users] Behavior of nested ellipses

> I don’t see why one is better than the other. I was surprised that the ellipsis which 'x' varies over changes between the pattern and the template. But it looks like no one else has the same intuition, so it's fine :-). > Yes. See this part of the documentation of `syntax`: That's clear,

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

Thanks Philip for these ideas, I won't be able to test all the suggestions today (due to time zone ;) but here is what I got so far: * My timezone is for Warsaw, Poland * When I create a file it is added with a correct timestamp but "raco pkg" downloads it and saves with + 1 hour timestamp. When

Re: [racket-users] Re: compile-zo: date for newly created .zo file ... is before source-file date ... which appears to be in the future

I don't really know, but a few thoughts: - I'm very suspicious about the daylight savings time possibility. Would you be comfortable sharing your specific timezone? - It might be helpful to see the results of file-or-directory-modify-seconds

Re: [racket-users] The Nitty Gritty of Pixels, Pens, and Lines example output

I've pushed an edit to the docs that attempts to address this point. https://github.com/racket/htdp/commit/86900c00e770f1336dafce331c206240495a9953 Robby On Sat, Mar 24, 2018 at 3:44 PM, Stephen Smith wrote: > Hi Everyone, > > When running the following example

[racket-users] Resubmitting PRs after build problems

Hi all, I have noticed that some recent PRs have failed the Travis CI build step seemingly due to unrelated, perhaps infrastructure-y, problems. e.g. The PR I submitted, via a Github edit that fixes a typo in a comment, failed the tests on one target with a tcp-connect timeout error (errno=60).