The entry menu inside a mounted archive offers write back, discard and unmount
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start in src/keymap/menu.rs with EntryFacts and entry_rows, then compare how make menu rows fire commands in src/app/view_state.rs and how archive commands are handled in src/app/archive/command.rs. Add menu rows for write, discard, and unmount with the stated change and capability conditions, routing clicks through the typed command path. Done when right-click and . show the applicable rows inside a mounted archive and each click runs its command.
Written by the indexing model from the issue text.
Description
The UX 2.0 plan (docs/archive/UX_2_0_PLAN.md §3a) planned a row on the entry menu inside a mounted archive: write back / discard / unmount (:archive write, :archive discard, :archive unmount). Write and discard would show only when the mount has changes, and write only where its Capability allows it. The plan shipped without them: inside a mount, the menu filters out refused rows but offers none of the archive's own operations, so they are reachable only by typing :archive ….
Expected: right-click (or .) on a member of a mounted archive shows those rows, each with its command as its key, applicable as above, and a click runs it through the same path the typed command takes.
Where: src/keymap/menu.rs (EntryFacts, entry_rows); a menu row firing a : command, as the make menu's rows fire :make <target> (HintEntry::Make in src/app/view_state.rs); src/app/archive/command.rs.
- Dominant language
- Rust
- Stars
- 17
- Forks
- 2
- Avg merge
- 39m
- Merged PRs (30d)
- 413
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Tripstack-Corp/spyc
-
area:agent type:fix
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Tripstack-Corp/spyc#1000 ·
Maintainers usually reply within 1 day
-
area:build-ci type:chore
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Tripstack-Corp/spyc#933 ·
Maintainers usually reply within 1 day
-
area:ui type:feat
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Tripstack-Corp/spyc#932 ·
Maintainers usually reply within 1 day
-
area:build-ci type:chore
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Tripstack-Corp/spyc#930 ·
Maintainers usually reply within 1 day
-
area:build-ci area:pane type:chore
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Tripstack-Corp/spyc#929 ·
Maintainers usually reply within 1 day
All issues in Tripstack-Corp/spyc
Similar issues
-
binding:python bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coollabsio/orbit#72 ·
Maintainers usually reply within 1 day
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relativeOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Nimblesite/osprey#370 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug order-flow studies ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
userFRM/egui-charts#2417 ·
Maintainers usually reply within 1 day