`dynamic-place` works like (I believe) `dynamic-require`, which starts
in `(current-load-relative-directory)`. If you want to use it in a
file and get consistent file-relative behavior, I suggest using
`define-runtime-path` or `quote-module-path`.
On Mon, Jan 22, 2018 at 11:48 AM, 'Royall Spence' via Racket Users
> In the docs for places (https://docs.racket-lang.org/reference/places.html),
> the example shows creating a place like so:
> (dynamic-place "place-worker.rkt" 'place-main)
> When I do this on LInux (haven't tried other systems yet), the search path
> starts at my home directory and fails to find the file. It's not a huge
> problem since I can invoke it with the full path:
> (dynamic-place (build-path (current-directory) "place-worker.rkt")
> but this does seem like either an error in the docs or in the behavior of
> the dynamic-place procedure. At first I was thinking our other `path-spec?`
> procedures start with the current module's directory, but then I noticed it
> actually uses a `module-spec?`. The only other time I really use that,
> though, is for `require`, which certainly does start in the current module's
> Should I submit a change in the docs? In the procedure? Am I barking up the
> wrong tree?
> 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.
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
For more options, visit https://groups.google.com/d/optout.