Limit watch-history depth
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Expected behavior of the wanted feature
There should be an option to limit the number of files that can be stored in watch-history, when the limit is hit for number of files, all entries for the file that it has been longest since viewing should be deleted to make way for the next file.
Alternative behavior of the wanted feature
No response
Log File
No response
Sample Files
No response
Contributor guide
No contributing guide indexed for this repository
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 locating the watch-history implementation and the configuration entry point for its storage limit. Verify how entries are grouped by file and determine the existing tests or test area for watch-history behavior; done means an option limits stored files and removes all entries for the least recently viewed file when the limit is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100