Suggestion: Capture at least some options
Open
Nobody has claimed this yet.
- Dominant language
- Vim Script
- Stars
- 1.9k
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
Hi Tim:
Don't capture options and maps. Options are sometimes mutilated and maps just interfere with updating plugins.
I agree about mappings, but I think It would be pretty useful to save path and tags, and even allow to pass them as options to :Obsession, that way every session could be more like an IDE project, but ala Vim. What do you think?
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 at the :Obsession entry point and review how session files currently handle options and maps. The proposal mentions preserving path and tags and accepting them as :Obsession options; done would require an agreed scope and behavior for those values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100