Skip to content
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

Jump to bottom

Add vi editing mode to REPL #7986

Closed
scabug opened this issue Nov 20, 2013 · 3 comments
Closed

Add vi editing mode to REPL #7986

scabug opened this issue Nov 20, 2013 · 3 comments
Assignees
@retronym
Labels
enhancement repl won't fix

Comments

@scabug
Copy link

scabug commented Nov 20, 2013

The scala REPL doesn't respect ~/.inputrc options, in particular vi editing mode.

Other interpreters, such as mysql, python, and irb all work correctly with this. This makes it inconvenient for vim users to use the interpreter, as it's slow to use the arrow keys and the delete keys to move around and make changes in a character-by-character basis (e.g. can't cw to change word).

Here is an example of inputrc settings that should be respected:

set editing-mode vi
set keymap vi
@scabug
Copy link
Author

scabug commented Nov 20, 2013

Imported From: https://issues.scala-lang.org/browse/SI-7986?orig=1
Reporter: Dionysis Zindros (dionyziz)

@scabug
Copy link
Author

scabug commented Nov 21, 2013

@som-snytt said:
Actually, they upgraded jline in 2.11 and it works viishly. I have a little shrine to Adriaan in the corner here and I light a candle every time I use the REPL. It's like being transported from the Dark Ages to sometime in 1977. But some commands balk.

@scabug
Copy link
Author

scabug commented Apr 28, 2016

@retronym said:
As noted above, this is something that can be configured now that we are tracking the standard JLine releases.

Caveat: We're about to upgrade to JLine 2.14.1 which changes the meaning of set keymap = vi to start the shell in edit mode. Discussion: scala/scala#5129 (comment)

We're now suggesting that issues around JLine itself should be raised in its issue tracker: https://github.com/jline/jline2.

If the issue is with our usage of JLine (or maybe, the fact we aren't on the latest version with a bug fix or feature you need), feel free to raise issues here. If you're not sure, ask us over on https://gitter.im/scala/contributors

@scabug scabug closed this as completed Apr 28, 2016
@eed3si9n eed3si9n mentioned this issue Jan 4, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@retronym retronym

Labels
enhancement repl won't fix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@retronym @scabug