Whenever I change code in my package I switch over to the terminal and 
recompile it with `raco setup`. This is slightly tedious and I’d like to be 
able to do this from within DrRacket. But I’m not sure how to translate the 
command `raco setup --doc-index --check-pkg-deps --tidy --unused-pkg-deps 
--pkgs <pkgname>` into a runnable racket module. I tried the following:

   1. Using `system*` didn’t work because it doesn’t search `$PATH` and so 
   it can’t find `raco`.
   2. Using `(find-executable-path "raco")` didn’t work either, it just 
   returned false.
   3. Trying to invoke the setup command using `dynamic-require` and 
   `raco/all-tools` *started* `raco setup` successfully, but then failed 
   because for some reason the setup command was trying to read and tidy up 
   stale DrRacket-specific zos (the stuff in `compiled/drracket` 
   subdirectories).

What should I do here?

-- 
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