Some kind of data-flow-based highlighting is an interesting idea – you could take
x = f(y, z) and colour
x as a mix of
z's colours, too. It would be fairly hard to do well, I think, but it would definitely be worth a shot.
Reducing the opacity is a nice way to distinguish functions from variables without making them really pop out – I'll play around with it a bit. For the record, I do think that bold functions work nicely with your theme. Oh, and no problem!
About the data-flow-highlighting: While it does sound pretty neat in theory, I'm not at all sure if it can be implemented in any reasonable fashion. Might have to look into that... I think I'll just throw together a sketch for something a bit more feasible (hopefully).
About backtraces: Sadly, there still are some cases where it's not terribly helpful yet. One case that is pretty annoying for my style of development:
There's a function defined in some file and I try to call it within that same file. But if I've made a mistake in the function definition the line numbers displayed in the error message is about the representation of that function in
init.jl and the line numbers displayed aren't the ones I would want to see.
I like that idea for highlighting matching variables. It'd probably be fairly straightforward to prototype something like that if you're interested in having a go.
Could you give me an example of the kind of backtraces you're getting? That's exactly what I had tried to fix, on my system backtraces are very to-the-point. Are you sure you have the latest Jewel.jl code (the fix isn't in a released version yet)?
pwd) yields /Applications/LightTable.app/Contents/Resources/app.nw. Is the expectation to launch a terminal client instead?
.CodeMirror-linebackground.error) that isn't implemented anywhere else.
juliafrom the repos, then
Pkg.add("Jewel"), finally I install the
Jupiterplugin in Light Table, but I get this error: http://bit.ly/UXFvG8