At Wed, 26 Oct 2016 15:16:03 -0400, David Storrs wrote:
> On Wed, Oct 26, 2016 at 2:30 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
> > At Wed, 26 Oct 2016 14:01:15 -0400, David Storrs wrote:
> >>       What is "-l-" ?  (That's an "ell", right?  Not a 1 / pipe /
> >> etc.)  I would have expected a space between the -l (--lib) and the
> >> "-".  Is it a typo?
> >
> > Yes, it's an "ell", and not a typo. `-l- raco` is short for `-l raco
> > --`, where `--` causes any later argument that start with "-" to be
> > passed on to `raco` instead of treated as a flag to `racket`.
> 
> Ah, good to know.  Is that a Racket-specific thing or a bit of
> Unix-ish lore that I've not encountered?  Google is not telling me.

Yes, the convention of abbreviating multiple "-" flags with a single
"-" is Unix-ish (second bullet):

 https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html

> >> 3)  Email someone the new "target" executable which they can run on
> >> their Windows machine.
> >>
> >> Is this right?
> >
> > Yes, although I bet you'll need
> >
> >  racket -G /path/to/windows/etc -X /path/to/windows/collects \
> >         -l- raco pkg install -i <pkg>
> >
> > to install some packages that "target.rkt" uses, since the unpacked
> > ".tgz" will have only the "base" package.
> 
> Probably this would happen first, right?  Unroll the Windows tgz, then
> install the packages, then do the cross-compilation?

Yes.


> On a separate but related note:  I would like to be able to contribute
> to the docs, both of core Racket and of various packages.  Is there a
> clear tutorial anywhere on that?  If so I can take the above and add
> it to the docs for cross compilation.
> 
> I know that in general this consists of sending a git pull request,
> but there are quite a few repositories (https://github.com/racket),
> and it's not obvious at all where the docs (Guide, Reference, etc)
> reside.  I've done quite a bit of fruitless exploring and finally
> given up.

You're right that it's not obvious where to find the source.

Clicking a section title effectively tells you the module path of the
enclosing document's source, since it tells how to link to a section.
For example, clicking "6.14 API for Cross-Platform Configuration" shows

  @secref["cross-system" #:doc '(lib "scribblings/raco/raco.scrbl")]

You could use DrRacket's "Open Require Path..." menu to open
"scribblings/raco/raco.scrbl".

Then, it's still some detective work to figure out that section "6.14"
would be in the 6th `include-section` which is "setup.scrbl", while the
path of the source file gives you a hint that it's in the package
"racket-doc". Finally, "pkgs.racket-lang.org" gives the source of
"racket-doc" as

   git://github.com/racket/racket/?path=pkgs/racket-doc

So, it's in the "racket/racket" repo on GitHub, specifically in the
"pkgs/racket-doc/scribblings/raco" subdirectory.

In short, a pull request at https://github.com/racket/racket would be
welcome.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to