[racket-users] DrRacket & current-compile

[kalime...@gmail.com]

Hello!
Is it possilble to redefine current-compile inside DrRacket?
I want to wrap compiler call for my #lang, but don't know how.
I tried racketrc.rktl, but it works only in console Racket.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/f264c15a-5e2a-45d2-884e-babbf8ea2acbn%40googlegroups.com.

Re: [racket-users] Re: scribble: referencing two identifiers with the same name?

[Robby Findler]

Oh! Thanks!

Perhaps DrRacket's button should include the +m flag.

Robby


On Mon, May 3, 2021 at 10:37 AM Sam Caldwell  wrote:

> Ah, I meant what happens when I open up my scribble file in DrRacket and
> press the "Scribble HTML" button. Maybe it would be more accurate to
> describe that as a plugin than DrRacket itself?
>
> -Sam Caldwell
>
> On Mon, May 3, 2021 at 11:24 AM Robby Findler 
> wrote:
>
>> On Mon, May 3, 2021 at 10:19 AM Sam Caldwell  wrote:
>>
>>> When I first ran Ryan's example, the reference to `racket:let` did not
>>> resolve to the proper link. After further investigating, this appears to be
>>> due to scribble's default behavior of not loading extra cross-referencing
>>> information [1]. If instead of `raco scribble`, I run `raco scribble +m`
>>> the link does resolve to the proper location. It also appears that DrRacket
>>> uses the +m option by default.
>>>
>>>
>> Just a minor point of clarification: DrRacket uses the documentation
>> built by `raco setup`; it doesn't build the docs itself. This is the same
>> build of the docs you see with `raco docs`.
>>
>> Robby
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/CALuKBHvJFmaJB9nf9%2BSDRAR6HUNa2pXeC0eaRfJ7VQ1quiC4_w%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAL3TdONURvPexFUbFeRPeNap8Y%2B4cRjRS-XBMWPK-hOPQFqVGQ%40mail.gmail.com.

Re: [racket-users] Re: scribble: referencing two identifiers with the same name?

[Sam Caldwell]

Ah, I meant what happens when I open up my scribble file in DrRacket and
press the "Scribble HTML" button. Maybe it would be more accurate to
describe that as a plugin than DrRacket itself?

-Sam Caldwell

On Mon, May 3, 2021 at 11:24 AM Robby Findler 
wrote:

> On Mon, May 3, 2021 at 10:19 AM Sam Caldwell  wrote:
>
>> When I first ran Ryan's example, the reference to `racket:let` did not
>> resolve to the proper link. After further investigating, this appears to be
>> due to scribble's default behavior of not loading extra cross-referencing
>> information [1]. If instead of `raco scribble`, I run `raco scribble +m`
>> the link does resolve to the proper location. It also appears that DrRacket
>> uses the +m option by default.
>>
>>
> Just a minor point of clarification: DrRacket uses the documentation built
> by `raco setup`; it doesn't build the docs itself. This is the same build
> of the docs you see with `raco docs`.
>
> Robby
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CALuKBHvJFmaJB9nf9%2BSDRAR6HUNa2pXeC0eaRfJ7VQ1quiC4_w%40mail.gmail.com.

Re: [racket-users] Re: scribble: referencing two identifiers with the same name?

[Robby Findler]

On Mon, May 3, 2021 at 10:19 AM Sam Caldwell  wrote:

> When I first ran Ryan's example, the reference to `racket:let` did not
> resolve to the proper link. After further investigating, this appears to be
> due to scribble's default behavior of not loading extra cross-referencing
> information [1]. If instead of `raco scribble`, I run `raco scribble +m`
> the link does resolve to the proper location. It also appears that DrRacket
> uses the +m option by default.
>
>
Just a minor point of clarification: DrRacket uses the documentation built
by `raco setup`; it doesn't build the docs itself. This is the same build
of the docs you see with `raco docs`.

Robby

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAL3TdOMVtxi6wjwRpPAPOB70pqAY36UjB2Cry0H0PpqoRcbE5Q%40mail.gmail.com.

Re: [racket-users] Re: scribble: referencing two identifiers with the same name?

[Sam Caldwell]

When I first ran Ryan's example, the reference to `racket:let` did not
resolve to the proper link. After further investigating, this appears to be
due to scribble's default behavior of not loading extra cross-referencing
information [1]. If instead of `raco scribble`, I run `raco scribble +m`
the link does resolve to the proper location. It also appears that DrRacket
uses the +m option by default.

So my current understanding is that there is no barrier to linking to other
forms if you rename them `for-label`, but if I want the same name to link
to different parts of the documentation I need to do something like the
Typed Racket example.

-Sam Caldwell

[1]
https://docs.racket-lang.org/scribble/running.html?q=scribble#%28part._xref-flags%29

On Sat, May 1, 2021 at 2:00 PM Ryan Kramer  wrote:

> Using the prefix should still link correctly. When I run the following
> program, it links to section 3.9 of the Racket Reference where `let` is
> defined. Does your link go somewhere else?
>
> ```
> #lang scribble/manual
>
> @(require (prefix-in racket: (for-label racket/base)))
>
> @defform[(let ([id expr] ...) body ...)]{
>  The same behavior as @(racket racket:let).
> }
> ```
>
> If you really want to remove the prefix, I don't know of any easier way
> than what you've already found. However, as a reader of the documentation I
> don't mind seeing the prefix. In fact, I think I would prefer to see it
> because then I can make a very good guess that it is talking about Racket's
> `let` without hovering or clicking the link.
>
> On Friday, April 30, 2021 at 11:01:20 AM UTC-5 sa...@ccs.neu.edu wrote:
>
>> Is there an easy way to refer to two different identifiers with the same
>> name when writing scribble documentation?
>>
>> For example, let's say I have a language with a `let` binding that
>> operates more or less the same as racket's `let`. I wanted to write
>> something like this:
>>
>> ```
>> @(require (prefix-in racket: (for-label racket/base)))
>>
>> @defform[(let ([id expr] ...) body ...){
>> The same behavior as @racket[racket:let].
>> }
>> ```
>>
>> This doesn't seem to work; the reference to racket's `let` ends up
>> including the `racket:` prefix and doesn't seem to resolve to the
>> appropriate link.
>>
>> I looked at Typed Racket's docs to see how it manages this problem, and
>> found the following pattern:
>>
>> ```
>> @(module def-racket racket/base
>>(require (for-label racket/base) scribble/manual)
>>(define let-id (racket let))
>>(provide let-id))
>>
>> @(require 'def-racket)
>>
>> @defform[(let ([id expr] ...) body ...){
>> The same behavior as @|let-id|.
>> }
>> ```
>>
>> source:
>> https://github.com/racket/typed-racket/blob/master/typed-racket-doc/typed-racket/scribblings/reference/special-forms.scrbl
>>
>> So my question is, is there an easier/more direct way to accomplish this
>> (perhaps since these typed racket docs were written)?
>>
>> It also looks like this pattern could be captured by a macro---has
>> someone written that already?
>>
>> Thanks,
>> Sam Caldwell
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/334007f4-0632-4814-8d22-9ad56f650d21n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CALuKBHsNBmvrNYpTE_hSvp%3D6-gTxQCerhC-Gr4bkf5-gHGLp%3Dg%40mail.gmail.com.

[racket-users] ACM Workshop on Functional Art, Music, Modelling and Design - Last Call for Papers, Demos, and Performances

[Michael Sperber]

Less than 2 weeks to go!

===
  7th ACM SIGPLAN International Workshop on
 Functional Art, Music, Modelling and Design
(FARM)
   Call for Papers, Demos, and Performance
   Virtual, 27th August 2021
  Deadlines:
   May 15 (Papers & Demos)
June 13 (Performances
   https://functional-art.org/2021
===

Key Dates
=

Papers and Demos:
Paper submission deadline   May 15
Author notification June 5
Camera readyJune 26
WorkshopAugust 27

Performances:
Performance submission deadline  June 13
Performance notification June 26

Call for Papers
===

After an 2020 online edition restricted to the performance session,
the ACM SIGPLAN International Workshop on Functional Art, Music,
Modelling and Design (FARM) will also be held online in 2021 but open
to all tracks (paper, demo and performance). Pursuing its mission,
this 9th workshop aims to bring together people who are harnessing
functional techniques in the pursuit of creativity and artistic
expression.

FARM encourages submissions from across art, craft, and design,
including textiles, visual art, music, 3D sculpture, animation, GUIs,
video games, 3D printing and architectural models, choreography,
poetry, and even VLSI layouts, GPU configurations, or mechanical
engineering designs. Theoretical foundations, language design,
implementation issues, and applications in industry or the arts are
all within the scope of the workshop.

In addition to the main workshop, FARM hosts a traditional evening of
performances. Thus, this call encompasses both papers/demos for the
workshop (and its published proceedings) as well as performance
proposals for the evening’s event. Authors are invited to make a
single submission for each. Authors may submit both a paper/demo and
performance proposal, but the submissions will be considered
independently.

Note on Finances


Paid registration to the FARM workshop is usually required for paper
and demo submitters, but will be waived for performers.

If you would have financial difficulty attending, you can apply for
conference “PAC” funds. Please get in touch for more information.

Submission
==

We welcome submissions from academic, professional, and independent
programmers and artists. Submissions are accepted via the Submission
page on Easychair:

https://easychair.org/conferences/?conf=farm2021

Paper proposals
===

Paper submissions are invited in three categories:

- Original research
- Overview / state of the art
- Technology tutorial (especially tools and environments for distributed 
artistic workflow)

All submissions must propose an original contribution to the FARM
theme. FARM is an interdisciplinary conference, so a wide range of
approaches are encouraged. An original paper should have 5 to 12
pages, be in portable document format (PDF), and use the ACM SIGPLAN
style guides and ACM SIGPLAN template (using the SIGPLAN
sub-format). Accepted papers will be published in the ACM Digital
Library as part of the FARM 2021 proceedings.

Authors are encouraged to submit auxiliary material for publication
along with their paper (source code, data, videos, images, etc.);
authors retain all rights to the auxiliary material.

Demo proposals
==

Demo proposals should describe a demonstration to be given at the FARM
workshop and its context, connecting it with the themes of FARM. A
demo could be in the form of a short (1020 minute) tutorial,
presentation of work-in-progress, an exhibition of some work, or even
a performance. Demo proposals should be in the form of an extended
abstract (500 to 2000 words). A demo proposal should be clearly marked
as such, by prepending “Demo Proposal:” to the title and proposed to
the ‘paper’ track. Demo proposals will be published on the FARM
website.

Performance proposals
==

FARM seeks proposals for performances which employ functional
programming techniques, in whole or in part. We invite a diverse range
of functionally-themed submissions including music, video, dance, and
performance art. Both live performances and fixed-media submissions
are welcome. We encourage both risk-taking proposals that push forward
the state of the art and refined presentations of highly developed
practice. Performances will be held online.

Performance proposals should be emailed to
performa...@functional-art.org, and must include: a description of the
performance (please be as specific as possible), an explanation of the
use of functional programming in the work, and a list of technical
requirements. All proposals should be supported by a link to an audio
or video ex