Readline shortcuts behave differently in the Console and Terminal panes

[georgestagg]

Positron Version:

Positron Version: 2023.12.0 (Universal) build 1539
Code - OSS Version: 1.85.0
Commit: a22c813
Date: 2023-12-12T03:09:20.555Z
Electron: 25.9.7
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.1.0

Steps to reproduce the issue:

1. Type something in the Console window, but don't execute it.
2. Try to use a readline shortcut such as ctrl-a.
3. Do the same thing in the Terminal window.

What did you expect to happen?

I would expect the same behaviour for readline shortcuts in both Console and Terminal panes, if the process in the Console uses readline (I was using R).

Additionally, when readline shortcuts are shared with other shortcuts, I would personally expect the readline shortcuts to win when the cursor is active in the console -- particularly for well-known ones such as ctrl-a and ctrl-e.

At the moment it looks like readline always wins when in the Terminal pane, but in Console sometimes Positron shortcuts (ctrl-a, ctrl-r, ctrl-w) win, sometimes readline works OK (ctrl-e, ctrl-k), and sometimes nothing seems to happen (ctrl-p).

Were there any error messages in the output or Developer Tools console?

No.

[dhruvisompura]

Mega-Triage 2/5/2025:
The following readline shortcuts work: ctrl+a and ctrl+e.
The remaining shortcuts may or may not work.