Skip to content

input and explore don't seem to recognize emacs-like navigation keybindings #17201

@yilisharcs

Description

@yilisharcs

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

  1. run input

  2. type "foo bar"

  3. type any of the keybindings listed above

  4. run explore

  5. type :

  6. 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 cde5f7b
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

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:needs-triageAn issue that hasn't had any proper look

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions