summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJon Dowland <jon@ra.ncl.ac.uk>2008-12-02 15:08:00 +0000
committerJon Dowland <jon@ra.ncl.ac.uk>2008-12-02 15:08:00 +0000
commit0da57d28de59b74ddcd8d0f2e97efc64592d0a61 (patch)
treef6dec69ea0fd19e4e5478ae198cb2f8e1dd09f53
parent6e9ec937fadd1b12d13f2fb4a5c7fea20ab4bb13 (diff)
mark this bug as done
-rw-r--r--doc/bugs/lockedit_plugin_should_alert_user_about_an_invalid_pagespec_in_preferences.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/lockedit_plugin_should_alert_user_about_an_invalid_pagespec_in_preferences.mdwn b/doc/bugs/lockedit_plugin_should_alert_user_about_an_invalid_pagespec_in_preferences.mdwn
index 21eb61df1..b8023ce87 100644
--- a/doc/bugs/lockedit_plugin_should_alert_user_about_an_invalid_pagespec_in_preferences.mdwn
+++ b/doc/bugs/lockedit_plugin_should_alert_user_about_an_invalid_pagespec_in_preferences.mdwn
@@ -15,3 +15,7 @@ Perhaps some validation should be performed on the pagespec and the form-submiss
> There are small classes of invalid pagespecs. For example, `(foo or bar`
> is invalid due to having unbalanced parens, while `foo or and bar`
> has invalid syntax. It's possible to detect these, I guess ... --[[Joey]]
+
+>> Having moved it to the .setup file makes things more obvious I think.
+>> Anyway I consider this [[done]], please de-done this if you disagree.
+>> --[[Jon]]