On Wed, 17 Apr 2013 17:25:02 +0200, Matthew Flatt <mfl...@cs.utah.edu>
wrote:
That matches my observations. Files accessed via collection always keep
their
paths 'as is'. But it is enough to start a program via racket <file>
instead of
racket -l what/ever to break this.
I should have mentioned that you could use `racket <full-path-to-file>'
to avoid the problem, which is a workaround that I have used often.
Thanks. I didn't know that. That seems to solve it for everything relying
on
the module path of the initial file.
Unfortunately, but understandably current-directory is not affected.
_________________________
Racket Developers list:
http://lists.racket-lang.org/dev
