@lrytz@som-snytt wdyt? I've tentatively milestoned it for 2.13.14.

if there is past history around this particular piece of code, I don't remember it. It came in in the big 2.13.12 JLine PR by Som (#8036)

@ckipp01 are you a good person to ask about the vi side of this...?

@ckipp01 are you a good person to ask about the vi side of this...?

meh, not really as I really don't use the REPL often. The reasoning here seems to make sense though.

I'm agnostic onSHELLOPTS but why remove support for

  -Xjline:<mode>                   Select JLine mode. Default: `emacs`, `help` to list choices.

drudgery of "run it again with this other option"...

➜  ~ scala -Xjline:helpUsage: -Xjline:<mode> where <mode> choices are emacs, vi, off (default: emacs).  emacs  emacs key bindings.  vi     vi key bindings  off    No JLine editing.

I see that works and is the reason I haven't had vi bindings in a while.

My "to do" list from Feb 20 says "learn more about using jline more effectively." Oh, that was Feb 20, 2016.

Edit: there is a PR about "where to put REPL files" and previous ticket(s) about "provide .rc or .inputrc support". It would be more of a clear win if there were a "private" .inputrc in the REPL-specific directory. Without knowing much about it, I'm wary of the global config problem.

Edit: I see the linked PR (which was finally merged at pandemic lockdown) links to the .inputrc support which was merged a year later. So maybe indeed just remove all the options.-D is my least favorite way of supplying config, however.

Good catch on the -Xjline. I'll review how it has been implemented.

I would remove even that since there is no point in having scala-specific way of configuring JLine.

Using the.inputrc is supported also by sbt.

I think the input mode should be personal and thus there is no reason to make it project-specific. It should be user specific and thus~/.inputrc is the correct place to define it.

While we could return back the-Jline it should not have a default value. If not defined, it would not change the way JLine defines its keymapping.

Note that-Jline:off is not the solution for emacs users since it turns jline completely off. This means that also wanted features, such as history, are turned off.

If@som-snytt you think that the-Jline option is needed for some reason, I can rework my PR to support it (with no default instead of havingemacs as the default), but personally I think it should be completely removed for the reasons I've discussed above.

Pushed a new version with-Jline deprecated and-Jnoline reinstated (although I don't know who would need it)