Integration with vdirsyncer
Open
Nobody has claimed this yet.
type: enhancement
type: question
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
This is an enhancement request:
- given that configuring two distinct programs is a mess for new users, resulting in lower khal adoption
- given that the vdirsyncer and khal authors seem to collaborate efficiently ;-)
I dream to see a better vdirsyncer/ikhal integration, such that:
- vdirsyncer is still an autonomous program (with a specific configuration file for autonomous use), but some of its functions are callable from ikhal,
- I only have to manage the khal configuration file, with vdirsyncer specific parameters inside,
- such parameters are transmitted by ikhal to vdirsyncer functions when needed,
- ikhal synchronize (with vdirsyncer functions) on start, may be ultimately in a separate thread to minimize start-up latency,
- when I type the '$' key (as with mutt) or when I quit ikhal, ikhal starts a (blocking) synchronization with vdirsyncer
Is my dream possible?
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 by reading the ikhal and vdirsyncer integration entry points; this issue names no files or tests. Determine how vdirsyncer functions could be configured through khal, synchronized at startup, and triggered by $ or quit. Done would require an agreed design and tests covering configuration and each synchronization trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100