REPL history only available after second expression.

[d-t-w]

Clojure 1.9, Java 1.8, Intellij 2.0.18.1.5, Cursive 1.7.0-2018.1

Apologies for the ridiculously minor bug ticket, but it's mildly annoying and presumably easy to address. Popped up a couple of Cursive releases ago I think.

1. Open a new REPL
2. Evaluate an SEXP
3. Press 'UP' key, expecting to move to (2)
4. No dice.
5. Evaluate another SEXP
6. Press 'UP' key, expecting to move to (5)
7. Works a charm, and can progress back to (2), behaviour as expected.

Starting nREPL server...
/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/bin/java -Dfile.encoding=UTF-8 -XX:-OmitStackTraceInFastThrow -Dclojure.compile.path=/Users/derek/troy-west/projects/cronut/target/classes -Dcronut.version=0.1.2-SNAPSHOT -Dclojure.debug=false "-javaagent:/Applications/IntelliJ IDEA.app/Contents/lib/idea_rt.jar=54330:/Applications/IntelliJ IDEA.app/Contents/bin" -classpath /Users/derek/troy-west/projects/cronut/test:/Users/derek/troy-west/projects/cronut/src:/Users/derek/troy-west/projects/cronut/test-resources:/Users/derek/troy-west/projects/cronut/dev-resources:/Users/derek/troy-west/projects/cronut/resources:/Users/derek/troy-west/projects/cronut/target/classes:/Users/derek/.m2/repository/integrant/integrant/0.6.3/integrant-0.6.3.jar:/Users/derek/.m2/repository/com/mchange/mchange-commons-java/0.2.11/mchange-commons-java-0.2.11.jar:/Users/derek/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar:/Users/derek/.m2/repository/org/clojure/tools.nrepl/0.2.12/tools.nrepl-0.2.12.jar:/Users/derek/.m2/repository/clojure-complete/clojure-complete/0.2.4/clojure-complete-0.2.4.jar:/Users/derek/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar:/Users/derek/.m2/repository/org/clojure/clojure/1.9.0/clojure-1.9.0.jar:/Users/derek/.m2/repository/com/stuartsierra/dependency/0.2.0/dependency-0.2.0.jar:/Users/derek/.m2/repository/org/clojure/core.specs.alpha/0.1.24/core.specs.alpha-0.1.24.jar:/Users/derek/.m2/repository/org/clojure/tools.logging/0.4.1/tools.logging-0.4.1.jar:/Users/derek/.m2/repository/org/quartz-scheduler/quartz/2.3.0/quartz-2.3.0.jar:/Users/derek/.m2/repository/org/slf4j/slf4j-api/1.7.25/slf4j-api-1.7.25.jar:/Users/derek/.m2/repository/com/mchange/c3p0/0.9.5.2/c3p0-0.9.5.2.jar:/Users/derek/.m2/repository/com/zaxxer/HikariCP-java6/2.3.13/HikariCP-java6-2.3.13.jar:/Users/derek/.m2/repository/org/clojure/spec.alpha/0.1.143/spec.alpha-0.1.143.jar clojure.main -i /private/var/folders/gz/7g238rvd6j1c_jrqqc87_7_m0000gn/T/form-init6058804289662690570.clj
objc[11875]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/bin/java (0x1068d34c0) and /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre/lib/libinstrument.dylib (0x10695f4e0). One of the two will be used. Which one is undefined.
Connecting to local nREPL server...
Clojure 1.9.0
nREPL server started on port 54332 on host 127.0.0.1 - nrepl://127.0.0.1:54332
(+ 1 1)
=> 2 ;; up key at this point has no effect
(+ 1 2)
=> 3 ;; up key at this point works as expected

[d-t-w]

Interestingly, I can only repeatedly reproduce this bug if I adjust the SEXP in step (2) to be one that definitely does not exist in the REPL history.

[danielcompton]

Also, I note that at step 6 I need to press the up key twice to get it to move back to show the previous REPL expression.

[cursive-ghost]

I just tried this, and I can't reproduce it. Even with a completely new Leiningen project (so no history) this works as I would expect.

[hjrnunes]

Further to @d-t-w's comment, it seems that pressing "UP", etc, works fine if it's the first thing you do.
e.g.

1. Open a new REPL
2. Press 'UP' key, expecting to move to last SEXP of previous REPL
3. Works a charm

However, the issue is there if you then enter a new SEXP.

[cursive-ghost]

Oh I see - so the problem is if you have an sexp in the REPL editor and then try to go up? I'll have another go at reproducing this tomorrow.