commit 8728911dd60ff7c9596836f602d4bfa71d9f4611
parent 1ee258506223effa8fa7d72a762786160cf921b3
Author: Anselm R. Garbe <garbeam@wmii.de>
Date: Sat, 20 May 2006 00:06:45 +0200
does my entry to TODO.wmii-4 makes sense?
Diffstat:
1 file changed, 20 insertions(+), 0 deletions(-)
diff --git a/TODO.wmii-4 b/TODO.wmii-4
@@ -38,3 +38,23 @@
- partial EWMH support
- libixp: idea from PoP: implement a va_args method similiar to printf for
marshalling 9P messages, might reduce LOC drastically
+
+
+23:55 <@garbeam> I currently think of something different I haven't done so far, but
+which might make some sense
+23:55 <@garbeam> I think of reporting an error if a specific command cannot be
+performed
+23:55 <@garbeam> (a write error with wmiir write)
+23:56 <@garbeam> e.g. if you do move next, and there is no next column, an error
+could be reported, thus one could add newcol next/prev instead
+23:56 <@garbeam> s/add/perform/
+23:57 <@garbeam> thiswould allow keeping the current behavior, but allowing your
+behavior as well, without screwing up things as they are
+23:57 <@garbeam> a column move command is a different question
+23:58 < John-Galt> that sounds reasonable
+Day changed to 20 May 2006
+00:00 <@garbeam> ie, if `xwrite /view/sel/sel/ctl move next` then xwrite
+/view/sel/sel/ctl newcol next; fi
+00:02 <@garbeam> I think moving columns is not necessary at all, it won't be used
+that often
+00:02 <@garbeam> John-Galt: what resolution do you got that you consider column
