In cases like these, I’d just define a helper file |my-commands.rkt|,
and |@(require "my-commands.rkt")| Those helper commands can use
standard Racket syntax, since they’re likely to mostly be
standard-looking Racket functions, and they can |(require
scribble/whatever)| libraries if they need to call some of the scribble
markup functions. You can also use standard |provide| forms in
|my-commands.rkt| to provide just your helper functions.
On 7/31/19 10:36 AM, Hendrik Boom wrote:
On Tue, Jul 30, 2019 at 10:40:34PM -0400, Hendrik Boom wrote:
On Tue, Jul 30, 2019 at 04:04:38PM -0400, Ben Greenman wrote:
Now for the next problem. If I @include-section, an occurrence of
redtext in the included section is recognised as an unbound identifier.
Evidently I need to say something to get included sections to inherit
bindings fro the main file.
`include-section` is much closer to Racket's `require` than TeX's `include`
I see.
So the included section has to do its own definition of redtext, or require
it from a common source.
IT WORKS NOW.
At the beginning of every inclided file (and there are more than fifty
of them) I have to place the lines
#lang scribble/base
@(require "pfx.scrbl")
where pfx.scrbl contains the definitions of my new @ commands.
I'm in the process of converting a huge multifile manuscript from
another adhoc and incomplete document compiler that also uses a
(partly incompatible) version of @-markup. Now that the performance
aspects of scribble have been dealt with, it's feasible. I'm looking
forward to using it.
-- hendrik
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-users/e9e61fdd-48f7-d8fa-e083-8eafe7bef2ac%40ccs.neu.edu.
