input and explore don't seem to recognize emacs-like navigation keybindings
Open
Nobody has claimed this yet.
status:needs-triage
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 79
Description
Bug report form
- I have done a basic search of the issue tracker to find any existing issues that are similar.
- I have checked that my version is at least the latest stable release available via my installation method.
Describe the bug
I observed that if I run input command, C-a, C-e, C-b, C-f, C-j, and C-u don't work. Ditto for the explore command, specifically when I type ":". I don't like that very much. Assuming this isn't a deliberate design decision, how can I help?
How to reproduce
-
run
input -
type "foo bar"
-
type any of the keybindings listed above
-
run
explore -
type :
-
Repeat steps 2 and 3 from the previous example
Expected behavior
Keybindings work.
Configuration
| key | value |
|---|---|
| version | 0.109.1 |
| major | 0 |
| minor | 109 |
| patch | 1 |
| branch | |
| commit_hash | cde5f7be8c813173e95ea65f96e79a133f587de7 |
| build_os | linux-x86_64 |
| build_target | x86_64-unknown-linux-musl |
| rust_version | rustc 1.89.0 (29483883e 2025-08-04) |
| rust_channel | 1.89.0-x86_64-unknown-linux-gnu |
| cargo_version | cargo 1.89.0 (c24e10642 2025-06-23) |
| build_time | 2025-12-02 20:32:41 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, network, plugin, rustls-tls, sqlite, static-link-openssl, trash-support |
| installed_plugins | gstat 0.106.1, inc 0.106.1, query 0.106.1 |
| experimental_options | example=false, reorder-cell-paths=true, pipefail=false, enforce-runtime-annotations=false |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the listed keybindings in the input command and in explore after typing :. Trace how those interactive entry points handle keyboard input, then verify that C-a, C-e, C-b, C-f, C-j, and C-u behave as expected in both contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100