-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the arrow keys in the REPL should cycle through recently used commands #54
Comments
Comment by gallais Note that you can use rlwrap to cope with the current limitations |
Comment by edwinb Yes, I run through |
Make it a little easier to debug IDE mode
Since idris2 is run as a script to chezscheme, is there no way to use chezscheme repl for autocomplete and stuff? |
Both Idris 1's REPL and Haskell's GHCi rely on haskeline for command-line interface, which in turn relies on haskell's POSIX and Win32 bindings. In the past, GHCi used to rely on editline, which is a set of bindings to libedit. Alternatively, ChezScheme's REPL "cafe" appears to be using scheme's native read and working just fine, with history and arrows working, so perhaps that could be somehow reused for the idris2 REPL? This would certainly lighten the load from the idris side - leaving it up to the underlying language to deal with the interactive command line. |
Is this still wanted given Edwin's comments on #807 (comment)?
|
Can this issue be closed? |
Yes. Official recommendation is to either:
|
This is a workaround for idris-lang/Idris2#54
@gallais I don't mind rlwrap solution but I am not sure if everyone is aware of it. Perhaps it shall be added to FAQ or readme? |
Issue by malte-v
Saturday Apr 18, 2020 at 07:29 GMT
Originally opened as edwinb/Idris2-boot#297
Currently using the arrow keys just prints ANSI sequences, which is different from the Idris 1 REPL.
Steps to Reproduce
Enter the Idris 2 REPL and use the arrow keys.
Expected Behavior
It cycles through the recently used commands.
Observed Behavior
Escape sequences get printed.
The text was updated successfully, but these errors were encountered: