diff options
| author | Tobias Brox <tobias@redpill-linpro.com> | 2017-01-24 09:39:12 +0100 |
|---|---|---|
| committer | Tobias Brox <tobias@redpill-linpro.com> | 2017-01-24 09:39:12 +0100 |
| commit | a97c5e2a011cbaa0e8baf405a21eaa33bf8c3024 (patch) | |
| tree | b4563c4c42c7bc77417da4044b952095bc263499 /README.md | |
| parent | 0a43da5e09aa164f30926762a54a50cefb1d4b1e (diff) | |
| download | calendar-cli-a97c5e2a011cbaa0e8baf405a21eaa33bf8c3024.zip | |
Added pointer to gcalendar-cli, previously known as calendar-cli
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -3,9 +3,13 @@ calendar-cli Simple command-line CalDav client, for adding and browsing calendar items, todo list items, etc. As of version 0.11 it's even becoming a full-fledged task management tool. +Other tools +----------- + +There is another project out there, "Command-line Interface for Google Calendar", previously located at pypi under the calendar-cli name. It has now been renamed to gcalendar-cli to avoid name conflict, and is available at https://pypi.python.org/pypi/gcalendar-cli/ + There is a "competing" project at https://github.com/geier/khal - you may want to check it out - it's more mature but probably more complex. It's using a "vsyncdir" backend - if I've understood it correctly, that involves building a local copy of the calendar. The philosophy behind calendar-cli is slightly different, calendar-cli is supposed to be a simple cli-based caldav+ical client. No synchronization, no local storage. -*NOTE*: As of 2015-10, someone has uploaded a "Command-line Interface for Google Calendar" to pypi with the same name - https://pypi.python.org/pypi/calendar-cli/ - this is a different project! Support ------- @@ -88,7 +92,7 @@ The file may look like this: } ``` -Optionally, in addition (or even instead) of "default", other "sections" can be created and selected through the --config-section option. The rationale is to allow configuration for multiple CalDAV-servers to remain in the same configuration file. Later versions will eventually be capable of copying events, or putting events into several calendars. +Optionally, in addition (or even instead) of "default", other "sections" can be created and selected through the --config-section option. The rationale is to allow configuration for multiple CalDAV-servers, or multiple calendars on the same CalDAV-server to remain in the same configuration file. Later versions will eventually be capable of copying events, or putting events into several calendars. Remember to `chmod og-r ~/.config/calendar.conf` or `chmod 0600 ~/.config/calendar.conf` |