From a441c4c733d6c45fe11d85e8a6dd030fecd56ea8 Mon Sep 17 00:00:00 2001 From: tadam Date: Sat, 3 Apr 2010 02:39:20 +0000 Subject: [PATCH] Add reminder to investigate recursive commands for 2.6 ThomasAdam to work on this. --- docs/ChangeLog | 4 ++++ docs/todo-2.6 | 19 +++++++++++++++++-- 2 files changed, 21 insertions(+), 2 deletions(-) diff --git a/docs/ChangeLog b/docs/ChangeLog index ff79a8783..9a74f208d 100644 --- a/docs/ChangeLog +++ b/docs/ChangeLog @@ -1,3 +1,7 @@ +2010-04-03 Thomas Adam + * todo-2.6: + Add observation about recursive commands. + 2010-02-26 Viktor Griph * todo-2.6: diff --git a/docs/todo-2.6 b/docs/todo-2.6 index ac30fedc0..261feac23 100644 --- a/docs/todo-2.6 +++ b/docs/todo-2.6 @@ -4,7 +4,7 @@ Issues opened recently: 0 Issues closed recently: 2 (B.11, F.4) open / total -A. Release stopping bugs: 3 / 3 +A. Release stopping bugs: 4 / 4 B. Normal bugs: 0 / 11 C. To be verified: 0 / 27 D. To be discussed: 3 / 4 @@ -12,7 +12,7 @@ E. To do: 0 / 18 F. Distribution issues: 1 / 4 G. Testing: 3 / 5 -Total: 9 / 70 +Total: 11 / 73 - When you add/close an item give dates @@ -39,6 +39,21 @@ A. Release stopping bugs xdg-menys. [Thomas/Dan] + F.4 Investigate limiting destructive/recursive commands by placing a limit + on them? For example: + + Style foo InitialMapCommand Bar + DestroyFunc Bar + AddToFunc Bar I Exec exec xterm -T Bar + + Although we give the user enough rope here to hang themselves, the end + result is to quickly overload FVWM. But I am not happy with + artificially limiting this either if it's what the user meant. + + Note that this is not an isolated example, since there's any other + number of ways to do the same thing, but it needs considering. + [Thomas: 2010-04-03] + B. Normal Bugs -------------- -- 2.11.4.GIT