Fork me on GitHub
Martynas M12:06:26

Hey. How do I prevent values from REPL appearing in my echo area (the one at the bottom)? It doesn't give me much use and it also lags the UI as I have fat structs in REPL. And then everything jumps around without much point because when I move my cursor again the echo area clears up and then reappears in one second. The only thing I want is that nothing would jump as I investigate the data structure by moving with my text cursor. Reproduction: 1. Print this into REPL:

(println (->> (range 1000)
              (map (juxt identity (constantly {:key :item})))
              (into {})))
2. Go to REPL buffer and move your cursor onto the map's key or on the starting/ending paren of the data structure. 3. Result in the snapshot:


Consider using the Cider inspector for results of more than a few lines

Martynas M13:06:43

Wow, that's actually pretty good and I'll probably use it. But I only wanted to scroll through the lines in REPL and it was constantly jumping. It shouldn't be jumping randomly.


I don't use the REPL buffer, it's very limited. To avoid scrolling issues for large results then switch that buffer to fundamental mode (making it even more redundant) My advice is to evaluate code in source code buffers and use the inspector for larger results. keep the inspector open if you need to follow results as each expression is evaluated. Close the REPL buffer and try forget it's there..

Martynas M13:06:56

Alright. For me the inspector buffer doesn't have my evil-mode keybinds. Any suggestions on that? It says that the buffer is read-only but I'm not going to edit, I'm only going to move around. Edit: I miss my 5j and }} to move by paragraphs and G to go to the bottom. Edit2: I remember when I was opening the REPL to evaluate code into it and was constantly changing its namespace into the current one. I didn't know how to evaluate code from the source buffer. Maybe this is the next step :thinking_face: Edit3: Probably the read-only issue is with evil-mode itself Edit4: There is a thing called evil-motion-mode for read-only buffers. But it doesn't have <RET> and L bindings.


, e f evaluates the current top-level form , e e evaluated the previous form (s-exp) , e is the evaluation menu and gives lots of options, more that most people need When evaluating in a source buffer it uses the namespace of the source buffer, so you dont need to change anything, just evaluate


Evil key bindings seem to work in the inspector buffer for me, G gg, j , k, n , p, etc. I havent noticed any problems. There arent line numbers when its a data set from the example code you provided, so 5j will not work as this is a logical representation If you want to navigate, try evaluate to pretty print, , e p f etc.

Martynas M17:06:13

It doesn't matter whether there are line numbers. I made my line numbers work on my treemacs buffer and they work. So I can then add this mode into the hooks of treemacs and they'll work too. It's an incidental problem that emacs's special-mode prevents evil-mode motions and I can't enable evil-motion-state on that buffer by using a hook. I can enable the evil mode manually but then it disappears when I try to navigate.

Martynas M07:06:52

I still like cider-result better. And I can copy the result to do something with it later :thinking_face: I don't know why but cider-inspect seems to be overengineered and there is too much output. I don't care what classes there are. Maybe I'll care if I'll need to inspect a Java-based class but cider-result just works. Also evil keys don't work in cider-inspect whereas they work very well in cider-result.