Re: [racket-users] PLTCOLLECTS env var is not always in effect - Why?

In reply to Sage Gerard: $ racket (use-user-specific-search-paths) ;returns: #t clicking on .rkt file that opens the file in racket: (use-user-specific-search-paths) ;returns: #t On Saturday, June 5, 2021 at 5:06:37 PM UTC-6 Sage Gerard wrote: > What is the value of

Re: [racket-users] PLTCOLLECTS env var is not always in effect - Why?

What is the value of ([][use-user-specific-search-paths](https://docs.racket-lang.org/reference/collects.html?q=PLTCOLLECTS#%28def._%28%28quote._~23~25kernel%29._use-user-specific-search-paths%29%29)) in each case? On 6/5/21 6:39 PM, Don Green wrote: > When I run drracket v 8.1 the additional

[racket-users] PLTCOLLECTS env var is not always in effect - Why?

When I run drracket v 8.1 the additional collection is in effect as evidenced by: (current-library-collection-paths) returns: '(# # #) however when I open drracket by clicking on a .rkt file (current-library-collection-paths) returns: '( # #) How to fix this? -- You received this message

[racket-users] Re: Embedded Racket reimplementation for constrained hardware?

On Sat, 5 Jun 2021 06:45:44 -0700 (PDT), dbohdan wrote: >Has anyone tried making a small embedded implementation of Racket? I mean >"embedded" not in the sense of 8-bit microcontrollers but more powerful yet >still constrained devices, like routers with 64 MB RAM running Linux or the

[racket-users] Embedded Racket reimplementation for constrained hardware?

Has anyone tried making a small embedded implementation of Racket? I mean "embedded" not in the sense of 8-bit microcontrollers but more powerful yet still constrained devices, like routers with 64 MB RAM running Linux or the PlayStation 2. I think you don't have to work from scratch to make