<div dir="auto">This was indeed caused by a version mismatch Problem by having multiple versions installed. Thank you so much again for your help!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 16, 2019, 3:19 PM <<a href="mailto:bil@ccrma.stanford.edu">bil@ccrma.stanford.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That variable is in the pretty-print function in write.scm. There's an<br>
earlier (require write.scm) to load it. To see if it is being loaded,<br>
you can set *load-hook*:<br>
<br>
(set! (hook-functions *load-hook*)<br>
(list (lambda (hook)<br>
(format () "loading ~S...~%" (hook 'name)))))<br>
<br>
*pretty-print-cycles* is somewhat new, so the version of write.scm<br>
and lint.scm need to match. I'd check /usr/local/share/snd for<br>
an obsolete version of the file (I'm not sure how that would<br>
happen -- the makefile puts *.scm in the scripts directory<br>
if you use "install"). It might depend on your *load-path*.<br>
Now that I look at it, the *load-hook* argument does not always<br>
include the directory -- maybe it should if *load-path* is in use.<br>
strace probably could tell you which write.scm is being loaded,<br>
but it's very verbose.<br>
<br>
If you can start snd, and (require write.scm), print<br>
(outlet (funclet pretty-print))<br>
and you should see *pretty-print-cycles*.<br>
<br>
<br>
</blockquote></div>