Ben Lerner

Huh? The gray layer still is present, when you mouseover stack frames in our stack trace. Here's a tiny program that demonstrates the point: ``` tbl = table: x, y...

This is still an issue on the latest merge, as of 8/11/2020.

Let's address this in #332 #329

I like this. Conceptually, I think of it as three z-index layers: all the program and repl content, the gray "deemphasizing" later, and the topmost error message.

One idea: could we have a `compiled-gdrive` locator that uses the c.p.o.compiled directory's precompiled contents, instead of the c.p.o.shared directory's sources?

When I looked at the implementation, I thought I saw it said we ignored faces because they were system dependent... In any case, our documentation about text-font is woefully lacking...

ok, I'll close this, and make it a docs issue

Actually, no -- let's take this opportunity to *fix* `text-image` to eliminate the font-family field.

I'd say it should do exactly what it does in definitions: run the indenter, which probably will do nothing at all. Pyret doesn't use tab to produce spaces in output...

This can't be a CPO issue -- it's a semantic issue that requires compiler support to detect which names are unused. And it's a subtle idea: more generally, should we...