summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2016-04-04 19:29:26 +0200
committerTobias Brox <tobias@redpill-linpro.com>2016-04-04 19:29:26 +0200
commit5cb747bdd92f4212be47bbfce8fe4ffed56ce83d (patch)
treefb23cc6389d8fb1325c88872a0e3d1a7358d66df /README.md
parent9de70bc6c80d5ad7fb330adabed343a93af83658 (diff)
downloadcalendar-cli-5cb747bdd92f4212be47bbfce8fe4ffed56ce83d.zip
calendar-cli name conflict, ref issue #24
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 50c7ced..3ac8866 100644
--- a/README.md
+++ b/README.md
@@ -5,6 +5,8 @@ Simple command-line CalDav client, for adding and browsing calendar items, todo
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
-------