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:30:06 +0200
commita80661652ccf2361fafe76b1813949cc3290bebe (patch)
tree472dd71717950fb654066e578ba95b312e4b1c60 /README.md
parent277d79071653b6745bdf00c3b883efcee234a6f1 (diff)
downloadcalendar-cli-a80661652ccf2361fafe76b1813949cc3290bebe.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 efadf2e..4e41a7a 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
-------