Greg Pfeil

With 8000ae010b13d176e0e869f29f181feac2b0ef9a we are a bit closer – `var` (rather than `?var`) is handled correctly when it's a name variable, but not as a process variable.

What's needed to finish this (at least) is converting `substitute-variables` to return the substituted value, rather than modifying it in place. This should give us a similar behavior for process...

Here is a test case for what is left to do ``` (trigger {test-use ?y} (trigger {use y} {should-be-use y})) (trigger {test-shadow ?y} (trigger {shadow ?y} {should-be-shadow y})) {test-use {use}}...

`substitute-variables` is now non-mutating, and I added a method on SYMBOL, so the above example now works if you convert all the bare instances of `y` to `'y`. Now to...

The remaining bit of this may be related to issue #1. I basically need to do a thorough review of what gets evaluated when.

I added the test-case above to the source.

Sorry guys – yeah, the marmalade repo hasn’t been kept up to date. Someone else did the marmalade thing. I’ll look into updating it myself.

Could you try toggling the value of `solarized-broken-srgb` and see if that fixes the GUI colors? (and let me know what happens) As far as the terminal colors, in that...

Thanks for opening the first issue! What CL impl are you using? I think that `method-combination-expander-function` can only be expected to work on combinations defined with the long form of...

Well, ideally it _would_ work for all of them. However, the short-form and built-ins aren’t defined using a function and so they can be handled specially, with the implementation only...