"explore -i with :try" doesn't allow arrow left/right navigation to edit command
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 79
Description
Describe the bug
The command line in :try mode in explore -i (see upper left in the screenshot below with "filter ()" written) doesn't seem to allow navigating the cursor back and forth with the left/right arrow keys to edit code inline. Instead you have to use Backspace to delete/rewrite. It's a small but quite annoying issue.
How to reproduce
- run
[[a,b];[1,2],[3,4]] | explore -i, then Return; - type
:try, then Return; - type some command/text and try navigating backwards with the arrow left key (←) [doesn't work on my machine].
Expected behavior
I'd expect to be able to use the Arrow left/right keys and edit the command inline.
Configuration
| key | value |
|---|---|
| version | 0.104.0 |
| major | 0 |
| minor | 104 |
| patch | 0 |
| branch | |
| commit_hash | |
| build_os | linux-x86_64 |
| build_target | x86_64-unknown-linux-gnu |
| rust_version | rustc 1.86.0 (05f9846f8 2025-03-31) (built from a source tarball) |
| cargo_version | cargo 1.86.0 (adf9b6ad1 2025-02-28) |
| build_time | 1980-01-01 00:00:00 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, sqlite, trash |
| installed_plugins | polars 0.104.0, query 0.104.0 |
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 issue with [[a,b];[1,2],[3,4]] | explore -i, then enter :try and inspect the interactive command-line handling used there. Done means left and right arrow keys move the cursor and allow inline editing of the command; add or update a regression test if the relevant test location is found.
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
- 45/100