Optimize away most expensive file prune calls, when refreshing

[git.ikiwiki.info.git] / doc / bugs / debbug_shortcut_should_expand_differently.mdwn

diff --git a/doc/bugs/debbug_shortcut_should_expand_differently.mdwn b/doc/bugs/debbug_shortcut_should_expand_differently.mdwn
index 22a1c149c1aa4b0ff02b2303cb0d3303a02c9e2c..b93b20a321f500bd77d1f34afd97f93777c7c2f1 100644 (file)
--- a/doc/bugs/debbug_shortcut_should_expand_differently.mdwn
+++ b/doc/bugs/debbug_shortcut_should_expand_differently.mdwn
@@ -1,4 +1,4 @@
-`\[[debbug 123456]]` expands to "bug #123456", which is hyperlinked. Could you please drop the leading "bug", for two reasons?
+`\[[!debbug 123456]]` expands to "bug #123456", which is hyperlinked. Could you please drop the leading "bug", for two reasons?

 
 First, #123456 is not a bug, it's a bug report. And second, #123456 suffices, doesn't it? By hardcoding the "bug" in there, you make it impossible to start a sentence with a bug number, e.g.:
 
 
 First, #123456 is not a bug, it's a bug report. And second, #123456 suffices, doesn't it? By hardcoding the "bug" in there, you make it impossible to start a sentence with a bug number, e.g.:
 


@@ -9,3 +9,9 @@ instead of
   There are problems with code. bug #123456 is a good example of...
 
 Thanks, --[[madduck]]
   There are problems with code. bug #123456 is a good example of...
 
 Thanks, --[[madduck]]

+
+> Tschwinge changed it to expand to "Debian bug #xxxx". Which happens to
+> sidestep the start of sentence problem. I think it makes sense to be
+> explicit about whose bug it is, in general -- but you can always edit the
+> shortcuts page for your own wiki to use something shorter and more
+> implicit. --[[Joey]] [[done]]