Name: Anonymous 2011-10-31 13:45
Where does Linux keep `graphical-read-eval-print-loop` stuff?
It worked fine on Windows.
It worked fine on Windows.
$ mred
path->complete-path: second argument is not a complete path: "./"
=== context ===
loop
find-library-collection-paths
exception raised by exception handler: standard-module-name-resolver: collection not found: "mzlib" in any of: (); original exception raised: path->complete-path: second argument is not a complete path: "./"
reference to undefined identifier: graphical-read-eval-print-loop