Btw, you can even press enter at the end of a sexpr to just copy/past this sexpr. Handy sometimes, in particular because s-expr navigation doesn’t work in past interactions for some reason. Now that I pay a little more attention to it, I think I move the cursor to past interaction more than I thought.

good to know

What’s the reason for having two kinds of pict-snip% ? If I make a pict and let drracket render it, then copying the resulting snip produces an instance of the one from drracket/drracket/private/pict-snip.rkt, which isn’t usable as a pict: it doesn’t have a get-pict or read-special, nor is it pict-convertible. But manually constructing an instance of the one from pict/snip produces a snip that can be used as a pict. If I make the printer render picts as pict/snip snips, and possibly copy them into code that gets saved, are there any issues lurking there to be aware of?

iirc there is something in the docs about duplicating snips in general - i don’t thing

think what you describe is specific to picts (I’m probably wrong)

One drawback of a pict/snip snip is that background expansion is unhappy with it : open-input-file: cannot open module file module path: (lib snip-wxme.rkt pict) path: /Applications/...t v7.7/share/pkgs/pict-doc/pict/snip-wxme.rkt system error: no such file or directory; rktio_err=3 .