Make history prediction location aware

Open
#3,472 4 comments 3 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
csharp, powershell
Domain
cli

Research direction

Start by tracing the existing history-based prediction and its current fallback strategy. Define how the working directory is stored and matched, then verify that predictions differ for matching locations and fall back to the current strategy when no location-specific history exists.

Written by the indexing model from the issue text.

Description

Area-HistoryImprovements Area-Predictors Issue-Enhancement
Prerequisites
  • Write a descriptive title.
Description of the new feature/enhancement

Include the current location (working directory) as part of history so that predictions based on history would show commands used from that location previously. If nothing is found, then fallback to current strategy.

Example:

> cd ~/repos/powershell
~/repos/powershell> git re

# prediciton would be something like: git reset --hard upstream/master

> cd ~/repos/somethingelse
~/repos/somethingelse> git re

# prediction would be something like: git reset --hard upstream/main
# in this example, you use `main` instead of `master` branch
Proposed technical implementation details (optional)

No response

Dominant language
C#
Stars
4.4k
Forks
341
No merged PRs in 30d

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 PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.