--- a/mcabber/ChangeLog Thu Jul 14 21:45:23 2005 +0100
+++ b/mcabber/ChangeLog Thu Jul 14 23:21:52 2005 +0100
@@ -1,6 +1,7 @@
mcabber (0.6.4-dev)
-
+ * One Ctrl-C does not terminate mcabber anymore (the 2nd Ctrl-C do), but
+ abort current completion
-- Mikael, ?
--- a/mcabber/TODO Thu Jul 14 21:45:23 2005 +0100
+++ b/mcabber/TODO Thu Jul 14 23:21:52 2005 +0100
@@ -20,10 +20,10 @@
* Handle message type "error"
* Show status changes in buddy window (if open)?
* Options completion
+* Configuration file parsing: parse as commands (set, alias, bind)
* Auto away
-* Maybe Ctrl-c should not (immediately) quit mcabber. What about:
- - 1 Ctrl-c leaves completion/multi-line modes
- - 2 Ctrl-c in less than 2 seconds leave mcabber
+* Add a sample script for the events command
+* Make first Ctrl-C leave multi-line mode
* Keep track of buddy resources. Ex.:
- buddy A connects with resource r1
- buddy A connects with resource r2
@@ -49,6 +49,7 @@
- /auth request|send [jid]
- /search <jid>|name
(server search)
+ - status status Message
- /help
- /rawxml...