With the downside of doing the install twice, right? Anyway, thanks for the help.

Maybe it’s a glitch but suddenly this morning it’s as if https://www.cs.utah.edu/plt/installers/6.11/racket-6.11-x86_64-linux.sh is throttled and timing out for Travis CI but works fine (so far) when I try it from home. 6.11 is just an example. Other versions, too. So for instance I’m seeing Travis CI jobs fail due to 10 minute time out: https://travis-ci.org/github/greghendershott/racket-mode/jobs/678674598 That were working fine even an hour ago. But I’ve been revising some tests and doing lots of CI runs this morning, so if http://utah.edu\|utah.edu had any throttling, that might be why…? idk

OK well maybe the universe is telling me it’s a good time to break for food, and try this again later.

I don’t know about http://utah.edu\|utah.edu but Github has been having trouble today

is there such a document as “Racket for Schemers”? i.e. the main things that somebody used to Scheme would need to know when getting started with Racket. I’m reading the Racket Guide and a lot of it is covering ground that I am familiar with already.

I wrote a macro called contents to generate document sections for a sugar library that matches the collects/racket file system. https://github.com/zyrolasting/idiocket/blob/master/scribblings/sections.rkt

It’s used here: https://github.com/zyrolasting/idiocket/blob/master/scribblings/idiocket.scrbl

The table of contents shows nothing and I do not see the sections in the index, but no error was reported on setup. What did I do wrong?

I found an error in a path predicate. I may update this question if I run into another problem.

Hi @sam.halliday there is the ‘1.4 A Note to Readers with Lisp/Scheme Experience’ in the Racket Guide: https://docs.racket-lang.org/guide/intro.html#%28part._use-module%29

Yep, changing my question: Is there an example of someone generating sections using both scribble/extract and hand-typed docs? This is my attempt, but the content from (include manual-path) ends up outside of the intended section. The only reason why I’m using include at all is because I don’t want the hand-typed manual to change the surrounding document structure.

(define-for-syntax (has-srcdoc? stx) (with-handlers ([exn:fail? (const #f)]) (dynamic-require `(submod ',(syntax->datum stx) srcdoc) 'get-docs (const #f)))) (define-syntax (idiocket-section stx) (syntax-case stx () [(_ modpath) (with-syntax ([mp (format-id #'modpath "idiocket/~a" (syntax-e #'modpath))] [manual-path (format "~a" (syntax->datum #'modpath))]) #`(begin (section (tt (symbol->string 'mp))) (defmodule mp) #,@(if (has-srcdoc? #'mp) #'((include-extracted mp)) #'()) (include manual-path)))]))

Ah yes, I seen that, thanks. I was hoping to learn the bits beyond Scheme though :slightly_smiling_face:

i.e. the Racket Guide minus the bits I already know from Scheme

it’s fine, I’ll just approach it fresh