The Racket repository
![]() These result from something like @racket[(x y)] being treated by Scribble as multiple RktXXX items rather than one. As a result the Markdown emitted was: `(``x`` ``y``)` But obviously instead we want: `(x y)` Kludgosity alert: Although it would probably be more-correct to consolidate the RktXXX items at the Scribble structure level, I don't easily see how. `@racket` is baking in the concept of Racket lexing (classifying text as various kinds of Racket elements). This is handy when the render will be HTML or Latek, and is benignly N/A when it will be plain text. But it's a bit square-peg/round-hole when the render will be Markdown. Rather than attempt to "un-lex" the Scribble structures (I'm having trouble seeing how), I'm handling it "after-the-fact" -- adjusting the generated Markdown text. If anyone thinks the preceding is an elaborate rationalization for an ugly kludge, I wouldn't argue, but I would need some help understanding the preferable way to go about it. |
||
---|---|---|
collects | ||
doc | ||
man/man1 | ||
src | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
README |
The Racket Programming Language =============================== Instructions for building Racket from source are in src/README. The main executables in this package: * DrRacket: Racket's integrated development environment (start here!). * racket: command-line tool for running Racket programs. * raco: command-line tool for compilation, documentation, and more. More Information ---------------- For Racket documentation, use DrRacket's `Help' menu, run the `Racket Documentation' application (Windows or Mac OS X), or run `raco docs' from a command line. Visit us at http://racket-lang.org/ for more Racket resources. License ------- Racket Copyright (c) 2010-2013 PLT Design Inc. Racket is distributed under the GNU Lesser General Public License (LGPL). This means that you can link Racket into proprietary applications, provided you follow the rules stated in the LGPL. You can also modify Racket; if you distribute a modified version, you must distribute it under the terms of the LGPL, which in particular means that you must release the source code for the modified software. See doc/release-notes/COPYING.txt for more information.