-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] support organizer & attendees fields #627
Comments
This is probably related to #580. At least the under-the-hood bits. |
This really depends on what you want from these. Just showing these is simple, actually sending out invitation is harder, replying to invitations more so and proper RFC 5546 support (see #132) will be a clusterfuck. This is coming though, the only question is when. Specifying what functionality you expect/want will help me prioritize. |
I'm personally interested in the showing part, as I use (i)khal only in read-only mode, as another script pulls events from exchange server and adds them into khal. |
This pull request just allow to use the {calendar} format. |
It would be great to see these fields as read-only at least . I'm using "khal printics" to see the details of an invitation from mutt e-mail client, however these fields are missing if I'm not wrong. |
Showing something like this should be easily doable: Attendees:
- John Smith <[email protected]>
- Sarah Smith <[email protected]> I think PRs would be welcome. Any comments, @geier ? |
totally agree, we need this, long term proper support for also answering those requests would still be great, but any step towards that goal is still very welcome. |
In the changelog I see that from 0.10.5 it is possible to add attendees using interactive mode. Is there also a way to add them using the cli? For the project khalorg I work around this issue by first creating a new event (khal new), then find for the newly created event using |
Would you consider supporting these fields familiar from the ical format?
The text was updated successfully, but these errors were encountered: