Matthew Flatt writes:
> At Sat, 11 Jul 2020 10:36:33 -0600, Matthew Flatt wrote:
>> Following up on Sam's suggestion, I recommend `xfvb-run` as something
>> like
>>
>> xfvb-run racket -l handin-server
>
> Should be `xvfb-run`. I always have trouble getting those letters in
> the right order.
We
Matthew Flatt writes:
> At Sat, 11 Jul 2020 10:36:33 -0600, Matthew Flatt wrote:
>> Following up on Sam's suggestion, I recommend `xfvb-run` as something
>> like
>>
>> xfvb-run racket -l handin-server
>
> Should be `xvfb-run`. I always have trouble getting those letters in
> the right order.
W
Matthew Flatt writes:
> At Sat, 11 Jul 2020 10:36:33 -0600, Matthew Flatt wrote:
>> Following up on Sam's suggestion, I recommend `xfvb-run` as something
>> like
>>
>> xfvb-run racket -l handin-server
>
> Should be `xvfb-run`. I always have trouble getting those letters in
> the right order.
W
Great, thanks for all of that digging. Ya, i think i will go the
non-declare_modules, non-ctool route for now as i think this fits my
use-case pretty well. I want to allow access to the full racket library for
racket code that changes often.
Nate
On Mon, Jul 13, 2020 at 8:32 PM Matthew Flatt wr
> There is another way: syntax-local-introduce will remove the macro scope.
`syntax-local-introduce` is no longer useful for this purpose since the
switch to the scope sets model. Other scopes, such as module scopes, will
often distinguish the macro-introduced name. For example, using
`syntax-l
5 matches
Mail list logo