Started working on a kal vs calendar-cli project split, as suggested by @fauxmight . Updates https://github.com/tobixen/calendar-cli/issues/88

2 files changed, 3 insertions, 2 deletions

diff --git a/README.md b/README.md
index 7e1187c..f2337e8 100644
--- a/README.md
+++ b/README.md
@@ -3,6 +3,8 @@ calendar-cli
 
 Simple command-line CalDav client, making it possible to add calendar events, browse an agenda and doing task management towards a caldav server.
 
+THIS IS THE LEGACY VERSION.  I got a bit unhappy with the project (particularly the quite different user interfaces when handling events vs handling tasks), so rather than making version 1.0, I decided to recreate it from scratch.  Please visit https://github.com/tobixen/kal for the new version (though be aware that it still has some sharp edges).
+
 Other tools
 -----------
 
diff --git a/calendar_cli/cal.py b/calendar_cli/cal.py
index 466c4eb..e3ee0ee 100755
--- a/calendar_cli/cal.py
+++ b/calendar_cli/cal.py
@@ -887,7 +887,7 @@ def check_due(ctx, limit, lookahead):
         if input == 'ignore':
             continue
         elif input == 'split':
-            interactive_split_task(obj, ctx)
+            interactive_split_task(ctx, obj)
         elif input.startswith('postpone'):
             obj.set_due(parse_add_dur(due, input.split(' ')[1]), move_dtstart=True)
         elif input == 'complete':
@@ -1010,7 +1010,6 @@ def interactive_split_task(ctx, obj):
         default = f"Plan how to do {summary}"
         while True:
             summary = click.prompt("Name for the subtask", default=default)
-            import pdb; pdb.set_trace()
             default=""
             if not summary:
                 break