Working directory history box, similar to command history but for directories

Open
#2,582 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

No files, tests, or entry points are identified in the issue. Start by locating the existing command-history box and determine how directory visits and keyboard shortcuts should correspond to it. Done means a chronological directory history is available through the proposed navigation controls and behaves consistently with command history.

Written by the indexing model from the issue text.

Description

area:search enhancement triaged
Discord username (optional)

Luis#2191

Describe the solution you'd like?
Very frequently, terminal users are switching between multiple directories,
spending considerable time typing directory pathnames.

A "working directory history" box, similar to the command history box but
showing a chronological history of directories where the user has been,
would be really helpful. It could be opened by default with the down key
(as opposed to up for command history) or the page-up key.
Is your feature request related to a problem? Please describe.

No response

Additional context

I have used this feature in the past (with some personal program I wrote, but it's not stable enough to be used in combination with Warp), and it really makes a huge difference for some tasks that require continuously switching between directories.

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.