Improve the presentation of nrepl messages

[bbatsov]

The presentation of nREPL messages we currently use leaves a ton of room for improvement.

• we lack proper font-locking that would make it easier to figure out what is what
• even the standard message keys are displayed in different order in every message
• values are not properly indented
• sometimes several keys end up being displayed on the same line, which gets me every time (I just miss the second key)

[bbatsov]

This article might be useful for the font-locking code if anyone decides to tackle this, although we should get by just fine with some generic font-locking without the notion of keywords.

[Malabarba]

Font locking in the sense of font-lock-mode shouldn't be necessary. We can just propertize a specific face to every other sexp.

[bbatsov]

True. I mostly want top-level keys to stand out. Bonus points for properly font-locked, strings, nils, etc.

[dpsutton]

Did @Malabarba 's commit fully satisfy the request? I find myself reinventing lots of things in cider only to find out that the necessary features already exist, there's a pattern to follow, etc. If yall would put a few pointers in here I'd be happy to run through and work on this.

[Malabarba]

My commit only highlights the request's keys, which was the lowest-hanging of the fruits here. I feel that improves the readability significantly.

It would also be nice to have proper string font-locking and proper indentation, but these might be a little more difficult to do efficiently (without making the buffer supper slow) and they're really not high priority for me.

[bbatsov]

I'd say that ordering the request/response keys consistently should be relatively easy to do and would be very helpful as well. Tackling the bug with several keys getting displayed on the same line is also important.

[bbatsov]

@dpsutton This ticket is still yours if you want it. ;-)

[Malabarba]

Given that this only really affects the cider developers, and even we weren't bothered enough to actually do something significant about it, maybe it's not that relevant. People's effort might be better spent elsewhere.

[bbatsov]

While this is true, this issue still represents an open thread and requires way less effort than most open tasks we have. I've been trying to do some cleanup lately, as tasks really piled on in the past 5-6 months. Hopefully contributor activity will pick up, as I'm pretty short on time myself.

[harold]

After goofing around here for a bit, another potential improvement would be lining things up:

(-->
  code     "(defn map-sequence->dataset "Turns an infinite training se..."
  column   1
  file     "/home/harold/src/cortex/src/cortex/dataset.clj"
  id       "45"
  line     377
  ns       "cortex.dataset"
  op       "eval"
  session  "499ca8d8-43c8-40bf-aa19-ff369673ce4c"
)

cf. the extant

(-->
  code  "(defn map-sequence->dataset "Turns an infinite training se..."
  column  1
  file  "/home/harold/src/cortex/src/cortex/dataset.clj"
  id  "45"
  line  377
  ns  "cortex.dataset"
  op  "eval"
  session  "499ca8d8-43c8-40bf-aa19-ff369673ce4c"
)