Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
REPL command history
See original GitHub issueI see that REPL command history has been added through this pull request. However, I am not able to view the history with up and down arrows, and I can’t even use the left arrow to navigate in my current command line, whether I launch a script with the -i option or I launch dotnet-script directly. My terminal is xterm-256color in Kali Linux, dotnet-script version is 0.52.0.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
File History
Viewing previous versions of a file Once you've opened up File History, you can view previous versions of a file by using the...
Read more >[Question] Sly repl history navigation : r/DoomEmacs
Go to the previous repl command I had typed and executed? In both command-mode and insert-mode the cursor just moves up in the...
Read more >Node.js REPL history by Josh Sherman
It contains a history, sans any sort of time of execution, of the commands you've entered into the Node.js REPL. The most recent...
Read more >read eval print loop - History in Clojure REPL
I'm doing my first steps with Clojure, but for some reason the up/down keys don't allow me to step through the command history...
Read more >Accessing Julia REPL command history
In the BASH shell used on Linux and UNIX, the history command calls up a list of recent commands used and has many...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems that #417 broke command history.
Same issue on Konsole, on Kubuntu 23.04.