diff options
| author | Joey Hess <joey@kodama.kitenet.net> | 2008-07-21 11:33:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kodama.kitenet.net> | 2008-07-21 11:34:49 -0400 |
| commit | d5e65e582a34ae2494fee493ddcb2b959e4a4bce (patch) | |
| tree | 14bf1f7a604406ecb98523eda42c2e864321e1d0 /doc/todo | |
| parent | d13200f92b74aa3d4e315809c78f1c2ec6c925a7 (diff) | |
| parent | e3a84952715cdd625258e1695cb74898006c31f3 (diff) | |
Merge commit 'smcv/prefix'
Conflicts:
doc/news/version_2.49.mdwn
Also fixed the newest news file (and my wikiannounce script).
Diffstat (limited to 'doc/todo')
108 files changed, 212 insertions, 212 deletions
diff --git a/doc/todo/ACL.mdwn b/doc/todo/ACL.mdwn index 1e068cb07..6b23acfae 100644 --- a/doc/todo/ACL.mdwn +++ b/doc/todo/ACL.mdwn @@ -21,7 +21,7 @@ something, that I think is very valuable. >>>> Which would rule out openid, or other fun forms of auth. And routing all access >>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]] -Also see [[debbug 443346]]. +Also see [[!debbug 443346]]. I am considering giving this a try, implementing it as a module. Here is how I see it: @@ -30,10 +30,10 @@ Here is how I see it: for a given (user, page, operation), as in: <pre> - \[[acl user=joe page=*.png allow=upload]] - \[[acl user=bob page=/blog/bob/* allow=*]] - \[[acl user=* page=/blog/bob/* deny=*]] - \[[acl user=http://jeremie.koenig.myopenid.com/ page=/todo/* deny=create + \[[!acl user=joe page=*.png allow=upload]] + \[[!acl user=bob page=/blog/bob/* allow=*]] + \[[!acl user=* page=/blog/bob/* deny=*]] + \[[!acl user=http://jeremie.koenig.myopenid.com/ page=/todo/* deny=create reason="spends his time writing todo items instead of source code"]] </pre> @@ -43,5 +43,5 @@ Here is how I see it: Possibly could refer to other ACL pages, as in: <pre> - \[[acl user=* page=/subsite/* acl=/subsite/acl.mdwn]] + \[[!acl user=* page=/subsite/* acl=/subsite/acl.mdwn]] </pre> diff --git a/doc/todo/A_page_that_inlines_pages__61____34____42____34___results_in_unnecessary_feed_generation.mdwn b/doc/todo/A_page_that_inlines_pages__61____34____42____34___results_in_unnecessary_feed_generation.mdwn index 8a4a41971..543c346ac 100644 --- a/doc/todo/A_page_that_inlines_pages__61____34____42____34___results_in_unnecessary_feed_generation.mdwn +++ b/doc/todo/A_page_that_inlines_pages__61____34____42____34___results_in_unnecessary_feed_generation.mdwn @@ -3,7 +3,7 @@ getting regenerated even when I edited only a page that did not affect any feed. I found that the problem only occurs in the presence of a file that -contains \[[inline pages="*"]]. +contains \[[!inline pages="*"]]. > How is this unexpected? By inlining _every_ page in the wiki, you're > making that page depend on every other page; any change to any page in @@ -15,7 +15,7 @@ contains \[[inline pages="*"]]. > N+1th page that its PageSpec matches is a no-op. > --[[Joey]] -[[tag done]] +[[!tag done]] Here's a short script for replicating the bug. Just cut and paste this to a shell, (it will only muck in a new /tmp/ikiwiki-test directory @@ -23,7 +23,7 @@ that it will create): cd /tmp mkdir ikiwiki-test; cd ikiwiki-test; mkdir src - echo '\[[inline pages="blog/*"]]' > src/myblog.mdwn + echo '\[[!inline pages="blog/*"]]' > src/myblog.mdwn mkdir src/blog; echo "A blog entry" > src/blog/entry.mdwn echo 'use IkiWiki::Setup::Standard { srcdir => "src", @@ -41,7 +41,7 @@ that it will create): echo "not a blog entry" > src/not-a-blog.mdwn ikiwiki --setup setup ls -l --time-style=full-iso output/myblog/index.rss - echo '\[[inline pages="*"]]' > src/archives.mdwn + echo '\[[!inline pages="*"]]' > src/archives.mdwn ikiwiki --setup setup ls -l --time-style=full-iso output/myblog/index.rss echo "still not blogging" >> src/not-a-blog.mdwn @@ -58,7 +58,7 @@ Here's the tail of the output that I see for this command: done $ ls -l --time-style=full-iso output/myblog/index.rss -rw-r--r-- 1 cworth cworth 459 2007-06-01 06:34:36.000000000 -0700 output/myblog/index.rss - $ echo '\[[inline pages="*"]]' > src/archives.mdwn + $ echo '\[[!inline pages="*"]]' > src/archives.mdwn $ ikiwiki --setup setup refreshing wiki.. scanning archives.mdwn diff --git a/doc/todo/Account_moderation.mdwn b/doc/todo/Account_moderation.mdwn index a03abb196..6ef7a65f1 100644 --- a/doc/todo/Account_moderation.mdwn +++ b/doc/todo/Account_moderation.mdwn @@ -7,6 +7,6 @@ the account gets approved.) --[[JoshTriplett]] -[[tag soc]] +[[!tag soc]] [[wishlist]] diff --git a/doc/todo/Add_DATE_parameter_for_use_in_templates.mdwn b/doc/todo/Add_DATE_parameter_for_use_in_templates.mdwn index 859e6af95..c908f57c8 100644 --- a/doc/todo/Add_DATE_parameter_for_use_in_templates.mdwn +++ b/doc/todo/Add_DATE_parameter_for_use_in_templates.mdwn @@ -83,4 +83,4 @@ regenerate this one against that). -- 1.5.2.2 -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/Add_support_for_latest_Text::Markdown_as_found_on_CPAN.mdwn b/doc/todo/Add_support_for_latest_Text::Markdown_as_found_on_CPAN.mdwn index 0a509ae2a..222cd8c46 100644 --- a/doc/todo/Add_support_for_latest_Text::Markdown_as_found_on_CPAN.mdwn +++ b/doc/todo/Add_support_for_latest_Text::Markdown_as_found_on_CPAN.mdwn @@ -8,7 +8,7 @@ This patch allows IkiWiki to work with either of the two: > be a good idea to check out current git master before spending time on > patches in the future. Thanks for the work anyway.. --[[Joey]] -[[tag done]] +[[!tag done]] --- IkiWiki/Plugin/mdwn.pm.orig 2008-03-08 11:33:50.000000000 +0100 +++ IkiWiki/Plugin/mdwn.pm 2008-03-08 13:37:21.000000000 +0100 @@ -42,4 +42,4 @@ The above patch, which is against ikiwiki-2.40, should fix [[bugs/markdown_modul -- [[HenrikBrixAndersen]] -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn index 2439cd65f..da68b04c2 100644 --- a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn +++ b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn @@ -1,7 +1,7 @@ -[[tag wishlist]] -[[tag patch]] +[[!tag wishlist]] +[[!tag patch]] -In our team internal wiki, we wish to impose a policy that all edits must have a comment. Patch in [[debbug 450620]]. +In our team internal wiki, we wish to impose a policy that all edits must have a comment. Patch in [[!debbug 450620]]. > Good idea! I also hate empty commit comments, but I know that it's also a matter > of human mentality. Of course, you can forbid users to commit empty comments, diff --git a/doc/todo/BTS_integration.mdwn b/doc/todo/BTS_integration.mdwn index c3cd51e04..b504698c4 100644 --- a/doc/todo/BTS_integration.mdwn +++ b/doc/todo/BTS_integration.mdwn @@ -6,6 +6,6 @@ This seems somewhat difficult, as ikiwiki would need to maintain a cache of the [scmbug](http://www.mkgnu.net/?q=scmbug) might help here. --[[JoshTriplett]] -[[tag soc]] +[[!tag soc]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Bestdir_along_with_bestlink_in_IkiWiki.pm.mdwn b/doc/todo/Bestdir_along_with_bestlink_in_IkiWiki.pm.mdwn index 180355875..73157a326 100644 --- a/doc/todo/Bestdir_along_with_bestlink_in_IkiWiki.pm.mdwn +++ b/doc/todo/Bestdir_along_with_bestlink_in_IkiWiki.pm.mdwn @@ -45,4 +45,4 @@ This patch adds function bestdir() which returns best directory from the directo ---- -[[users/arpitjain]] -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/BibTeX.mdwn b/doc/todo/BibTeX.mdwn index 1ab0b2e81..1ac9e99b8 100644 --- a/doc/todo/BibTeX.mdwn +++ b/doc/todo/BibTeX.mdwn @@ -69,4 +69,4 @@ Any thoughts on the best way to proceed? --[[JasonBlevins]], March 23, 2008 21:41 EDT -[[tag soc]] [[tag wishlist]] +[[!tag soc]] [[!tag wishlist]] diff --git a/doc/todo/CGI_method_to_pullrefresh.mdwn b/doc/todo/CGI_method_to_pullrefresh.mdwn index 6b5824bd3..f01c2f65a 100644 --- a/doc/todo/CGI_method_to_pullrefresh.mdwn +++ b/doc/todo/CGI_method_to_pullrefresh.mdwn @@ -2,6 +2,6 @@ In some situations, it makes sense to have the repository in use by ikiwiki reside on a different machine. In that case, one could juggle SSH keys for the `post-update` hook. A better way may be to provide a different `do` parameter handler for the CGI, which would pull new commits to the working clone and refresh the wiki. Then, the remote `post-update` hook could just `wget` that URL. To prevent simple DoS attacks, one might assign a simple password. -[[tag wishlist]] +[[!tag wishlist]] > [[done]] via the pinger and pingee plugins --[[Joey]] diff --git a/doc/todo/Configurable_minimum_length_of_log_message_for_web_edits.mdwn b/doc/todo/Configurable_minimum_length_of_log_message_for_web_edits.mdwn index 0210c38c3..7870281ae 100644 --- a/doc/todo/Configurable_minimum_length_of_log_message_for_web_edits.mdwn +++ b/doc/todo/Configurable_minimum_length_of_log_message_for_web_edits.mdwn @@ -1,3 +1,3 @@ It would be nice to specify a minimum length for the change log for web edits, and if it's only required vs. non-required. I realise this is not going to solve the problem of crap log messages, but it helps guard against accidental submissions which one would have logged. Mediawiki/wikipedia has that option, and I find it a useful reminder. --[[madduck]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Enable_filtering_of_files_indexed_for_search.mdwn b/doc/todo/Enable_filtering_of_files_indexed_for_search.mdwn index e9b3690d0..7e692dcd8 100644 --- a/doc/todo/Enable_filtering_of_files_indexed_for_search.mdwn +++ b/doc/todo/Enable_filtering_of_files_indexed_for_search.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist]] A useful item, I think, would be for an option to disable certain pages from being indexed. diff --git a/doc/todo/Gallery.mdwn b/doc/todo/Gallery.mdwn index ebfd437e6..fbf1802fd 100644 --- a/doc/todo/Gallery.mdwn +++ b/doc/todo/Gallery.mdwn @@ -28,9 +28,9 @@ That's one way to do it, and it has some nice benefits, like being able to edit --[[Joey]] -[[tag soc]] +[[!tag soc]] -[[tag wishlist]] +[[!tag wishlist]] ---- @@ -39,7 +39,7 @@ I have implemented the first version of the Gallery Plugin for Ikiwiki as part o Plugin can be downloaded from [here](http://myweb.unomaha.edu/~ajain/gallery.tar). It can be used as : <br> -\[[gallery imagedir="images" thumbnailsize="200x200" cols="3" alt="Can not be displayed" title="My Pictures"]] +\[[!gallery imagedir="images" thumbnailsize="200x200" cols="3" alt="Can not be displayed" title="My Pictures"]] where-<br> * imagedir => Directory containing images. It will scan all the files with jpg|png|gif extension from the directory and will put it in the gallery.<br> @@ -59,7 +59,7 @@ For any feedback or query, feel free to mail me at arpitjain11 [AT] gmail.com Additional details are available [here](http://myweb.unomaha.edu/~ajain/ikiwikigallery.html). -[[tag patch]] +[[!tag patch]] > I'd love to merge this into ikiwiki. > diff --git a/doc/todo/Give_access_to_more_TMPL__95__VAR_variables_in_templates_inserted_by_the_template_plugin.mdwn b/doc/todo/Give_access_to_more_TMPL__95__VAR_variables_in_templates_inserted_by_the_template_plugin.mdwn index 14dfa82d9..a644e236b 100644 --- a/doc/todo/Give_access_to_more_TMPL__95__VAR_variables_in_templates_inserted_by_the_template_plugin.mdwn +++ b/doc/todo/Give_access_to_more_TMPL__95__VAR_variables_in_templates_inserted_by_the_template_plugin.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist patch]] +[[!tag wishlist patch]] # Context @@ -54,7 +54,7 @@ of the pages tagged d1. My current plan is : -- thanks to the edittemplate plugin, `/view/dev/*` and `/view/howto/*` would contain respectively `\[[template id=dev_direction]]` and `\[[template id=howto_usage]]` +- thanks to the edittemplate plugin, `/view/dev/*` and `/view/howto/*` would contain respectively `\[[!template id=dev_direction]]` and `\[[!template id=howto_usage]]` - `/templates/dev_direction.mdwn` and `/templates/howto_usage.mdwn` would use `\[[!map ...]]` directives to build their views # My issue @@ -68,7 +68,7 @@ Where `BASENAME` value would be, e.g., `u1` or `d2`, depending on the page inserting the template. But `BASENAME` does not exist. I found that `<TMPL_VAR PAGE>` is replaced with the full path to the page, but I did not found how to get the page's basename in a template included -with a `\[[template id=...]]` directive. +with a `\[[!template id=...]]` directive. Any idea ? @@ -88,7 +88,7 @@ avoid the ad-hoc plugin solution. most possible of these pages. > The following patch adds a `basename` `TMPL_VAR` variable that can be -> used in the templates inserted by \[[template plugin]] : +> used in the templates inserted by \[[!template plugin]] : > diff --git a/IkiWiki/Plugin/template.pm b/IkiWiki/Plugin/template.pm > index a6e34fc..bb9dd8d 100644 diff --git a/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn b/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn index 3e596656d..d264bd209 100644 --- a/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn +++ b/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn @@ -10,4 +10,4 @@ subpage: `<current>/$tagbase/<tagname>`. See also: [[bugs/tags_base_dir_not_used_when_creating_new_tags]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Moving_Pages.mdwn b/doc/todo/Moving_Pages.mdwn index 38a5d3ad2..e1447bfb7 100644 --- a/doc/todo/Moving_Pages.mdwn +++ b/doc/todo/Moving_Pages.mdwn @@ -30,14 +30,14 @@ Brad > > This could also be implemented using a combination of raw inline and meta > to change the title (add a "redirected from etc." page. This could be done -> with a plugin. A redirect page would be [[redirect page="newpage"]]. +> with a plugin. A redirect page would be [[!redirect page="newpage"]]. > But then if you click "edit" on this redirect page, you won't be able > to edit the new page, only the call to redirect. > --Ethan ----- -[[tag patch]] +[[!tag patch]] This is my second cut at a feature like that requested here. It can also be found [here](http://ikidev.betacantrips.com/patches/move.patch). diff --git a/doc/todo/New_preprocessor_directive_syntax.mdwn b/doc/todo/New_preprocessor_directive_syntax.mdwn index b37985994..2215cc4b4 100644 --- a/doc/todo/New_preprocessor_directive_syntax.mdwn +++ b/doc/todo/New_preprocessor_directive_syntax.mdwn @@ -14,8 +14,8 @@ Making this transition would fix two major warts: * The inability to use spaces in wikilinks or link text * The requirement to use a trailing space on a preprocessor directive - with no arguments, such as `\[[toc ]]` + with no arguments, such as `\[[!toc ]]` --[[JoshTriplett]] -[[done]] in version 2.21, using the '!'-prefixed syntax. --[[JoshTriplett]]
\ No newline at end of file +[[done]] in version 2.21, using the '!'-prefixed syntax. --[[JoshTriplett]] diff --git a/doc/todo/OpenSearch.mdwn b/doc/todo/OpenSearch.mdwn index 467a7115a..e63ded688 100644 --- a/doc/todo/OpenSearch.mdwn +++ b/doc/todo/OpenSearch.mdwn @@ -1,6 +1,6 @@ [[plugins/search]] could provide [OpenSearch](http://www.opensearch.org/) metadata. Various software supports OpenSearch (see the Wikipedia article on -[[wikipedia OpenSearch]]); in particular, browsers like Firefox and Iceweasel +[[!wikipedia OpenSearch]]); in particular, browsers like Firefox and Iceweasel will automatically discover an OpenSearch search and offer it in the search box. diff --git a/doc/todo/Option_to_make_title_an_h1__63__.mdwn b/doc/todo/Option_to_make_title_an_h1__63__.mdwn index ff2997bee..efa07ad79 100644 --- a/doc/todo/Option_to_make_title_an_h1__63__.mdwn +++ b/doc/todo/Option_to_make_title_an_h1__63__.mdwn @@ -1,4 +1,4 @@ -Currently, the page title (either the name of the page or the title specified with `\[[meta title="..."]]`) shows up in a `<div class="header">`. I tend to follow the [w3c guideline recommending the use of h1 for the title](http://www.w3.org/QA/Tips/Use_h1_for_Title); for this purpose, how about an option to make the page title an `<h1 class="header">`, and shift the markdown headings down by one (making # an h2, ## an h3, etc; or alternatively making # equivalent to `\[[meta title="..."]]`)? +Currently, the page title (either the name of the page or the title specified with `\[[!meta title="..."]]`) shows up in a `<div class="header">`. I tend to follow the [w3c guideline recommending the use of h1 for the title](http://www.w3.org/QA/Tips/Use_h1_for_Title); for this purpose, how about an option to make the page title an `<h1 class="header">`, and shift the markdown headings down by one (making # an h2, ## an h3, etc; or alternatively making # equivalent to `\[[!meta title="..."]]`)? > The reason I don't use a h1 for the navbar is that while it incorporates > the page title, it's not just a page title, it has the links to parent pages. diff --git a/doc/todo/Overlay_directory_for_pagetemplates.mdwn b/doc/todo/Overlay_directory_for_pagetemplates.mdwn index 9d0524f1d..c4f261d03 100644 --- a/doc/todo/Overlay_directory_for_pagetemplates.mdwn +++ b/doc/todo/Overlay_directory_for_pagetemplates.mdwn @@ -6,4 +6,4 @@ Instead, I wonder whether it would be possible to create an overlay directory su [[madduck]]: Update: I did try setting `templates` in `ikiwiki.setup` but could not get it to work. Then I found in the code that ikiwiki already checks that dir before the `/usr/share/ikiwiki` one, and tried it again, and now it works... sorry. -Thus [[taglink done]].
\ No newline at end of file +Thus [[!taglink done]].
\ No newline at end of file diff --git a/doc/todo/RSS_fields.mdwn b/doc/todo/RSS_fields.mdwn index 8902f6426..54a2f98ad 100644 --- a/doc/todo/RSS_fields.mdwn +++ b/doc/todo/RSS_fields.mdwn @@ -22,4 +22,4 @@ new blog post is created, and then the edit link would work fine. > I would really like for some additional TMP variables to be present in the rss template as well. For the inline page template, the CTIME TMPL_VAR results in nice phrases like: <q>Posted late Tuesday morning, November 13th, 2007</q>, and it would be neat to let the planet Debian people see that as well :-) Manoj -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Raw_view_link.mdwn b/doc/todo/Raw_view_link.mdwn index 11673a6d8..e4f941743 100644 --- a/doc/todo/Raw_view_link.mdwn +++ b/doc/todo/Raw_view_link.mdwn @@ -10,4 +10,4 @@ The configuration setting for Mercurial could be something like this: > Not that I'm opposed to the idea of a plugin that adds a Raw link > --[[Joey]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn index 2d14c827d..a26433919 100644 --- a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn +++ b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn @@ -1,4 +1,4 @@ -[[tag patch]] +[[!tag patch]] Here's my next version of the patch - still a work in progress. @@ -6,7 +6,7 @@ It provides the following new features. The features are designed to preserve th * If you specify an event preprocessor in a post, such as: - [[event time="2008-06-24"]] + [[!event time="2008-06-24"]] That date will be used instead of the post creation time when displaying the calendar. diff --git a/doc/todo/Short_wikilinks.mdwn b/doc/todo/Short_wikilinks.mdwn index 05f894dfe..b9aec9112 100644 --- a/doc/todo/Short_wikilinks.mdwn +++ b/doc/todo/Short_wikilinks.mdwn @@ -58,9 +58,9 @@ Other alternatives would be > I agree that a plugin would probably be more cumbersome, but it is very > doable. It might look something like this: - \[[link bar]] + \[[!link bar]] - \[[link bar=VeryLongPageName]] + \[[!link bar=VeryLongPageName]] >> This is, however, still missing specifying the link text, and adding that option would seem to me to complicate the plugin syntax a lot, unless support is added for the |-syntax for specifying a particular parameter to every plugin. @@ -74,13 +74,13 @@ Other alternatives would be >> ... Returning to this, the syntax infact wouldn't be so bad with the |-syntax, given a short name for the plugin: [[whatever|ref 1]] - \[[ref 1=page_with_long_name]] + \[[!ref 1=page_with_long_name]] >>> A way to do this that doesn't need hacking at the preprocessor syntax >>> follows: --[[Joey]] - \[[link bar=1]] - \[[dest 1=page_with_long_name]] + \[[!link bar=1]] + \[[!dest 1=page_with_long_name]] >>>> But this doesn't work so well for links that aren't valid keys. Such >>>> as stuff with spaces in it. I'd like to be able to write any kind of @@ -88,8 +88,8 @@ Other alternatives would be >>>>> You're right, and to fix that it could be turned around: --[[Joey]] - \[[link 1=bar]] - \[[dest 1=page_with_long_name]] + \[[!link 1=bar]] + \[[!dest 1=page_with_long_name]] >> It also shouldn't be difficult to support non-wiki links in this same >> way, so that you could still link everywhere in an uniform manner, as diff --git a/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn b/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn index 998d7f0c2..c651b0a45 100644 --- a/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn +++ b/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn @@ -21,4 +21,4 @@ that we're at the root of a (sub-)hierarchy. > > IMHO, what you really want is [[Moving_pages]]. :-) --[[Joey]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Support_XML-RPC-based_blogging.mdwn b/doc/todo/Support_XML-RPC-based_blogging.mdwn index 3afbc59bc..f9685be73 100644 --- a/doc/todo/Support_XML-RPC-based_blogging.mdwn +++ b/doc/todo/Support_XML-RPC-based_blogging.mdwn @@ -1,6 +1,6 @@ Perhaps ikiwiki should support XML-RPC-based blogging, using the [standard MetaWeblog protocol](http://www.xmlrpc.com/metaWeblogApi). This would allow -the use of applets like [[debpkg gnome-blog]] to post to an ikiwiki blog. The +the use of applets like [[!debpkg gnome-blog]] to post to an ikiwiki blog. The protocol supports multiple blog names, so one standard URL with page names as blog names would work. --[[JoshTriplett]] @@ -9,6 +9,6 @@ blog names would work. --[[JoshTriplett]] >> I'd love to see support for this and would be happy to contribute towards a bounty (say US$100) :-). [PmWiki](http://www.pmwiki.org/) has a plugin which [implements this](http://www.pmwiki.org/wiki/Cookbook/XMLRPC) in a way which seems fairly sensible as an end user. --[[AdamShand]] -[[tag soc]] +[[!tag soc]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/Support_tab_insertion_in_textarea.mdwn b/doc/todo/Support_tab_insertion_in_textarea.mdwn index bed8381be..10d94343f 100644 --- a/doc/todo/Support_tab_insertion_in_textarea.mdwn +++ b/doc/todo/Support_tab_insertion_in_textarea.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist]] It'd be nice to be allowed to insert tabs into the textarea, as opposed to having to insert 4-spaces for lists/etc. This would require JavaScript to diff --git a/doc/todo/Support_wildcard_inside_of_link__40____41___within_a_pagespec.mdwn b/doc/todo/Support_wildcard_inside_of_link__40____41___within_a_pagespec.mdwn index 24f9054f7..2837634d9 100644 --- a/doc/todo/Support_wildcard_inside_of_link__40____41___within_a_pagespec.mdwn +++ b/doc/todo/Support_wildcard_inside_of_link__40____41___within_a_pagespec.mdwn @@ -2,7 +2,7 @@ I don't segregate my blog entries into a directory, but instead want my blog to simply consist of all pages that have been tagged. That is, I'd like to have my blog page look like this: - \[[inline pages="link(tag/*)"]] + \[[!inline pages="link(tag/*)"]] That doesn't work in ikiwiki 2.1, but I have it [working](http://www.cworth.org/blog) with the following patch: diff --git a/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn b/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn index 842c87e2d..61b19d302 100644 --- a/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn +++ b/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn @@ -1,4 +1,4 @@ -Here is a patch [[tag patch]] to add a *forward*ing functionality +Here is a patch [[!tag patch]] to add a *forward*ing functionality to the [[`meta`_plugin|plugins/meta]]. > [[done]], with some changes --[[Joey]] @@ -22,7 +22,7 @@ I can also submit a Git patch, if desired. **OPT_DELAY** = delay=**D** | empty (*immediatelly*) -\[[meta forward="**WHITHER**" **OPT_DELAY**]] +\[[!meta forward="**WHITHER**" **OPT_DELAY**]] # Extensions and Ideas diff --git a/doc/todo/absolute_urls_in_wikilinks.mdwn b/doc/todo/absolute_urls_in_wikilinks.mdwn index 50c2fe16f..a0fe83e44 100644 --- a/doc/todo/absolute_urls_in_wikilinks.mdwn +++ b/doc/todo/absolute_urls_in_wikilinks.mdwn @@ -1,8 +1,8 @@ -[[tag wishlist]] +[[!tag wishlist]] An option to have absolute urls in wikilinks instead of relative ones would be useful, for pages included into other pages out of the wiki rendering process (shtml for example) -since these pages can be included from a subdir. Ditto, links from \[[ inline ..]] or \[[map ..]]. +since these pages can be included from a subdir. Ditto, links from \[[!inline ..]] or \[[!map ..]]. > You can make a wikilink absolute by prefixing it with a /, see > [[ikiwiki/subpage/linkingrules/]]. Pagespecs match absolute by default. But what do @@ -10,11 +10,11 @@ since these pages can be included from a subdir. Ditto, links from \[[ inline .. > change. --Ethan >> I want the "last pages" in my sidebar. and some links to a few special pages. ->> \[[inline ]] or \\[[map ]] in the sidebar is a bad idea, (because each update rebuilds +>> \[[!inline ]] or \\[[!map ]] in the sidebar is a bad idea, (because each update rebuilds >> all the wiki), so I use server-side-include instead of the sidebar plugin; >> this reduces the dependencies >> my sidebar is generated as http://foo.org/menu/index.html, so all the links generated by ->> \[[inline ]] or \[[map ]] are relative to this position. +>> \[[!inline ]] or \[[!map ]] are relative to this position. >> Included from http://foo.org/section/sub/blah/index.shtml, the links are broken. >> >> — NicolasLimare diff --git a/doc/todo/aggregate_401_handling.mdwn b/doc/todo/aggregate_401_handling.mdwn index 4f7c96946..125e74e76 100644 --- a/doc/todo/aggregate_401_handling.mdwn +++ b/doc/todo/aggregate_401_handling.mdwn @@ -1,5 +1,5 @@ The aggregate plugin's handling of http 301 (moved permanently) could be -improved. Per [[rfc 1945]]: +improved. Per [[!rfc 1945]]: > The requested resource has been assigned a new permanent URL > and any future references to this resource should be done diff --git a/doc/todo/aggregate_to_internal_pages.mdwn b/doc/todo/aggregate_to_internal_pages.mdwn index 38427133f..272e146f4 100644 --- a/doc/todo/aggregate_to_internal_pages.mdwn +++ b/doc/todo/aggregate_to_internal_pages.mdwn @@ -56,4 +56,4 @@ change their pagespecs to use `internal()`. > "ikiwiki-transition aggregateinternal $setupfile" moves the pages around, > although it doesn't update the pagespecs (I wouldn't know how...) --[[smcv]] -[[tag patch done]] +[[!tag patch done]] diff --git a/doc/todo/allow_CGI_to_create_dynamic_pages.mdwn b/doc/todo/allow_CGI_to_create_dynamic_pages.mdwn index 6125bc413..7f51f79d0 100644 --- a/doc/todo/allow_CGI_to_create_dynamic_pages.mdwn +++ b/doc/todo/allow_CGI_to_create_dynamic_pages.mdwn @@ -1,3 +1,3 @@ -[[tag wishlist]] +[[!tag wishlist]] It would be cool if the CGI could be used to render dynamic pages. For instance, I might want to create a page with a `\[[map]]` according to a [[pagespec]] to be passed in the query string, instead of creating/hardcoding all possible pagespecs I might want to call. diff --git a/doc/todo/allow_full_post_from_the___34__add_a_new_post__34___form.mdwn b/doc/todo/allow_full_post_from_the___34__add_a_new_post__34___form.mdwn index 8ef8a1533..a604182b1 100644 --- a/doc/todo/allow_full_post_from_the___34__add_a_new_post__34___form.mdwn +++ b/doc/todo/allow_full_post_from_the___34__add_a_new_post__34___form.mdwn @@ -9,4 +9,4 @@ comment form. > I agree that having this as an option is reasonable. Although it would > take a fair amount of work. --[[Joey]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/attachments.mdwn b/doc/todo/attachments.mdwn index 430817d3f..56b2249ea 100644 --- a/doc/todo/attachments.mdwn +++ b/doc/todo/attachments.mdwn @@ -11,4 +11,4 @@ nice to add: srcdir. This would allow the admin to review them, and manually add/delete them before they bloat history. -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/auto-create_tag_pages_according_to_a_template.mdwn b/doc/todo/auto-create_tag_pages_according_to_a_template.mdwn index fac450a22..bfb4a863b 100644 --- a/doc/todo/auto-create_tag_pages_according_to_a_template.mdwn +++ b/doc/todo/auto-create_tag_pages_according_to_a_template.mdwn @@ -4,6 +4,6 @@ Tags are mainly specific to the object to which they’re stuck. However, I ofte Also see: <http://madduck.net/blog/2008.01.06:new-blog/> and <http://users.itk.ppke.hu/~cstamas/code/ikiwiki/autocreatetagpage/> -[[tag wishlist]] +[[!tag wishlist]] I would love to see this as well. -- dato diff --git a/doc/todo/automatic_use_of_syntax_plugin_on_source_code_files.mdwn b/doc/todo/automatic_use_of_syntax_plugin_on_source_code_files.mdwn index e9706653f..cd5ff34de 100644 --- a/doc/todo/automatic_use_of_syntax_plugin_on_source_code_files.mdwn +++ b/doc/todo/automatic_use_of_syntax_plugin_on_source_code_files.mdwn @@ -7,7 +7,7 @@ as the type argument. Together with the ability to have [[wiki-formatted_comments|wiki-formatted_comments_with_syntax_plugin]], -this would allow the use of ikiwiki for [[wikipedia literate programming]]. +this would allow the use of ikiwiki for [[!wikipedia literate programming]]. * I have started something along these lines see [[plugins/contrib/sourcehighlight]]. For some reason I started with source-highlight [[DavidBremner]] diff --git a/doc/todo/blogpost_plugin.mdwn b/doc/todo/blogpost_plugin.mdwn index aade457d0..60b1e2515 100644 --- a/doc/todo/blogpost_plugin.mdwn +++ b/doc/todo/blogpost_plugin.mdwn @@ -153,4 +153,4 @@ Index: IkiWiki.pm our $version='unknown'; # VERSION_AUTOREPLACE done by Makefile, DNE </pre> -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn b/doc/todo/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn index caff54780..0a036d315 100644 --- a/doc/todo/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn +++ b/doc/todo/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn @@ -1,6 +1,6 @@ I am serving notice that I am starting work on a calendar plugin inspired by Blosxom's calendar plugin. The current plan is to create a plugin that looks through all the source files matching a certain pagespec, and optionally spit out a month view for the specified month (default to current), or spit out a year view for a given year (defaulting to the current year), of a list of year with posts in them. The output would be a table, with the same CSS directives that the Blosxom plugin used to use (so that I can just reuse my css file). The links would be created to a $config{archivedir}/$year or $config{archivedir}/$year-$month file, which can just have - \[[inline pages="blog/* and !*/Discussion and creation_year($year) and creation_month($month)" rss="no" atom="no" show="0"]] + \[[!inline pages="blog/* and !*/Discussion and creation_year($year) and creation_month($month)" rss="no" atom="no" show="0"]] or some thing to generate a archive of postings. @@ -10,21 +10,21 @@ ManojSrivastava This plugin is inspired by the calendar plugin for Blosxom, but derivesno code from it. This plugin is essentially a fancy front end to archives of previous pages, usually used for blogs. It can produce a calendar for a given month, or a list of months for a given year. To invoke the calendar, just use the preprocessor directive: - \[[calendar ]] + \[[!calendar ]] or - \[[calendar type="month" pages="blog/* and !*/Discussion"]] + \[[!calendar type="month" pages="blog/* and !*/Discussion"]] or - \[[calendar type="year" year="2005" pages="blog/* and !*/Discussion"]] + \[[!calendar type="year" year="2005" pages="blog/* and !*/Discussion"]] The year and month entities in the out put have links to archive index pages, which are supposed to exist already. The idea is to create an archives hierarchy, rooted in the subdirectory specified in the site-wide customization variable, archivebase. archivebase defaults to "archives". Links are created to pages "$archivebase/$year" and "$archivebase/$year/$month". The idea is to create annual and monthly indices, for example, by using something like this sample from my archives/2006/01.mdwn - \[[meta title="Archives for 2006/01"]] - \[[inline rootpage="blog" atom="no" rss="no" show="0" pages="blog/* and !*/Discussion and creation_year(2006) and creation_month(01)" ]] + \[[!meta title="Archives for 2006/01"]] + \[[!inline rootpage="blog" atom="no" rss="no" show="0" pages="blog/* and !*/Discussion and creation_year(2006) and creation_month(01)" ]] I'll send in the patch via email. @@ -38,7 +38,7 @@ mailed me, and my response to it. --[[Joey]] > > I'm sending in an updated package, and have removed the older version you had here.--ManojSrivastava -[[tag patch]] +[[!tag patch]] ---- diff --git a/doc/todo/canonical_feed_location.mdwn b/doc/todo/canonical_feed_location.mdwn index b294e594a..694f67633 100644 --- a/doc/todo/canonical_feed_location.mdwn +++ b/doc/todo/canonical_feed_location.mdwn @@ -13,4 +13,4 @@ with all news or the one with the latest news only, I don't know yet.) >> wouldn't embed the feed link into `<head>` so that browsers can automatically >> find it. -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/clickable-openid-urls-in-logs.mdwn b/doc/todo/clickable-openid-urls-in-logs.mdwn index acf2c2d49..ab2a6b51f 100644 --- a/doc/todo/clickable-openid-urls-in-logs.mdwn +++ b/doc/todo/clickable-openid-urls-in-logs.mdwn @@ -6,7 +6,7 @@ for SVN. If this is OK, I'll patch the other RCS modules, too. > recognise such commit messages when parsing the logs. Do that and extend > to the other modules and I'll accept it. --[[Joey]] -[[tag patch]] +[[!tag patch]] <pre> --- IkiWiki/Rcs/svn.pm (revision 2650) diff --git a/doc/todo/color_plugin.mdwn b/doc/todo/color_plugin.mdwn index 069e2d4c2..cb3e85b74 100644 --- a/doc/todo/color_plugin.mdwn +++ b/doc/todo/color_plugin.mdwn @@ -23,7 +23,7 @@ What do you think about it? --[[Paweł|ptecza]] > `<span>`. A preprocessor directive is not really any less ugly than html > tags, though at least it could play nicely with nested markdown: --[[Joey]] > -> \[[color red,green """ +> \[[!color red,green """ > Xmas-colored markdown here > """]] diff --git a/doc/todo/conditional_text_based_on_ikiwiki_features.mdwn b/doc/todo/conditional_text_based_on_ikiwiki_features.mdwn index c6f1fefe1..4bdcf3d01 100644 --- a/doc/todo/conditional_text_based_on_ikiwiki_features.mdwn +++ b/doc/todo/conditional_text_based_on_ikiwiki_features.mdwn @@ -1,6 +1,6 @@ I'd like to see some way to conditionally include wiki text based on whether the wiki enables or disables certain features. For example, -[[ikiwiki/formatting]], could use `\[[if (enabled smiley) """Also, because +[[ikiwiki/formatting]], could use `\[[!if (enabled smiley) """Also, because this wiki has the smiley plugin enabled, you can insert \[[smileys]] and some other useful symbols."""]]`, and a standard template for [[plugins]] pages could check for the given plugin name to print "enabled" or @@ -52,7 +52,7 @@ Syntax could vary greatly here, both for the > As to the syntax, to fit it into standard preprocessor syntax, it would > need to look something like this: > -> \[[if test="enabled(smiley)" """foo"""]] +> \[[!if test="enabled(smiley)" """foo"""]] > > --[[Joey]] @@ -70,7 +70,7 @@ Syntax could vary greatly here, both for the >> >> A few use cases for `included`, which I would really like to see: >> ->> * On the sidebar page, you could say something like \[[if test="!included" +>> * On the sidebar page, you could say something like \[[!if test="!included" >> """This page, without this help message, appears as a sidebar on all >> pages."""]]. The help text would then only appear on the sidebar page >> itself, not the sidebar included on all pages. @@ -110,7 +110,7 @@ This is now completely [[todo/done]]! See [[plugins/conditional]]. Is there a way to test features other than plugins? For example, to add to [[ikiwiki/Markdown]] something like - \[[if test="enabled(multimarkdown)" then="You can also use..."]] + \[[!if test="enabled(multimarkdown)" then="You can also use..."]] (I tried it like that just to see if it would work, but I wasn't that lucky.) --ChapmanFlack diff --git a/doc/todo/correct_published_and_updated_time_information_for_the_feeds.mdwn b/doc/todo/correct_published_and_updated_time_information_for_the_feeds.mdwn index 082f0800c..565f3b16c 100644 --- a/doc/todo/correct_published_and_updated_time_information_for_the_feeds.mdwn +++ b/doc/todo/correct_published_and_updated_time_information_for_the_feeds.mdwn @@ -110,4 +110,4 @@ Index: IkiWiki/Plugin/inline.pm [[done]] --[[Joey]] -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/darcs.mdwn b/doc/todo/darcs.mdwn index 84c99daba..e757867d2 100644 --- a/doc/todo/darcs.mdwn +++ b/doc/todo/darcs.mdwn @@ -9,8 +9,8 @@ Here's Thomas Schwinge unfinished darcs support for ikiwiki. -- [Thomas Schwinge](mailto:tschwinge@gnu.org) -[[toggle text="show"]] -[[toggleable text=""" +[[!toggle text="show"]] +[[!toggleable text=""" # Support for the darcs rcs, <URL:http://darcs.net/>. # Copyright (C) 2006 Thomas Schwinge <tschwinge@gnu.org> # @@ -206,8 +206,8 @@ This is my ([bma](bma@bmalee.eu)) darcs.pm - it's messy (my Perl isn't up to muc `rcs_commit()` uses backticks instead of `system()`, to prevent darcs' output being sent to the browser and mucking with the HTTP headers (`darcs record` has no --quiet option). And `rcs_recentchanges()` uses regexes rather than parsing darcs' XML output. -[[toggle text="show" id="bma"]] -[[toggleable id="bma" text=""" +[[!toggle text="show" id="bma"]] +[[!toggleable id="bma" text=""" #!/usr/bin/perl @@ -334,8 +334,8 @@ This is my ([bma](bma@bmalee.eu)) darcs.pm - it's messy (my Perl isn't up to muc Well, here's my version too. It only does getctime -- using a real XML parser, instead of regexp ugliness -- and maybe recentchanges, but that may be bitrotted, or maybe I never finished it, as I only need the getctime. As for actual commits, I have previously voiced my opinion, that this should be done by the plugin generating a patch bundle, and forwarding it to darcs in some way (`darcs apply` or even email to another host, possibly moderated), instead of the hacky direct modification of a working copy. It could also be faster to getctime in a batch. Just reading in all the changes the first time they're needed, might not be a big improvement in many cases, but if we got a batch request from ikiwiki, we could keep reaing the changes until all the files in this batch request have been met. --[[tuomov]] -[[toggle text="show" id="tuomov"]] -[[toggleable id="tuomov" text=""" +[[!toggle text="show" id="tuomov"]] +[[!toggleable id="tuomov" text=""" <pre> #!/usr/bin/perl # Stubs for no revision control. @@ -484,4 +484,4 @@ I have addressed the recentchanges bit, you can find my hacked up darcs.pm at <h It's got couple of FIXMEs, and a very site-specific filter for recentchanges. Not sure how to do that better though. I will eventually add web commits, probably of my own (and mention it here). -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/datearchives-plugin.mdwn b/doc/todo/datearchives-plugin.mdwn index 4264b5895..5a5560d6c 100644 --- a/doc/todo/datearchives-plugin.mdwn +++ b/doc/todo/datearchives-plugin.mdwn @@ -74,4 +74,4 @@ created and populated with the relevant posts. A [[ikiwiki/Pagespec]] works perf >>> might move it to the contributed plugins directory as it's a bit >>> specialised to be included in ikiwiki though. --[[Joey]] -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/discussion_page_as_blog.mdwn b/doc/todo/discussion_page_as_blog.mdwn index 577ced17d..c7a3d6ac9 100644 --- a/doc/todo/discussion_page_as_blog.mdwn +++ b/doc/todo/discussion_page_as_blog.mdwn @@ -30,4 +30,4 @@ I don't think that the nesting is very clear, I found it confusing.. Would each page be its own individual blog? Or its own blog post? To me it seems like an entire wiki can be viewed as a blog, with threaded or unthreaded comments underneath. -[[tag soc]] +[[!tag soc]] diff --git a/doc/todo/discussion_page_as_blog/discussion/castle/discussion.mdwn b/doc/todo/discussion_page_as_blog/discussion/castle/discussion.mdwn index 10f7a066f..c95fb0e20 100644 --- a/doc/todo/discussion_page_as_blog/discussion/castle/discussion.mdwn +++ b/doc/todo/discussion_page_as_blog/discussion/castle/discussion.mdwn @@ -1 +1 @@ -[[inline pages="sandbox/castle/discussion/* and !sandbox/castle/discussion/*/*" rootpage="sandbox/castle/discussion"]]
\ No newline at end of file +[[!inline pages="sandbox/castle/discussion/* and !sandbox/castle/discussion/*/*" rootpage="sandbox/castle/discussion"]]
\ No newline at end of file diff --git a/doc/todo/discussion_page_as_blog/discussion/castle/discussion/Don__39__t_like_foo.mdwn b/doc/todo/discussion_page_as_blog/discussion/castle/discussion/Don__39__t_like_foo.mdwn index 65672f14e..48ca72a9c 100644 --- a/doc/todo/discussion_page_as_blog/discussion/castle/discussion/Don__39__t_like_foo.mdwn +++ b/doc/todo/discussion_page_as_blog/discussion/castle/discussion/Don__39__t_like_foo.mdwn @@ -1,3 +1,3 @@ I don't like foo. Have you tried living without foo? -[[inline pages="sandbox/castle/discussion/Don__39__t_like_foo/*" rootpage="sandbox/castle/discussion/Don__39__t_like_foo"]]
\ No newline at end of file +[[!inline pages="sandbox/castle/discussion/Don__39__t_like_foo/*" rootpage="sandbox/castle/discussion/Don__39__t_like_foo"]]
\ No newline at end of file diff --git a/doc/todo/done.mdwn b/doc/todo/done.mdwn index 0ad5656a0..ed161fb5b 100644 --- a/doc/todo/done.mdwn +++ b/doc/todo/done.mdwn @@ -1,3 +1,3 @@ recently fixed [[TODO]] items -[[inline pages="link(todo/done) and !todo and !*/Discussion" sort=mtime show=10]] +[[!inline pages="link(todo/done) and !todo and !*/Discussion" sort=mtime show=10]] diff --git a/doc/todo/doxygen_support.mdwn b/doc/todo/doxygen_support.mdwn index ae31c1603..4625da904 100644 --- a/doc/todo/doxygen_support.mdwn +++ b/doc/todo/doxygen_support.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist]] Given that ikiwiki has a suggested use as a tool for developers, I was thinking it might be cool if ikiwiki had [Doxygen](http://www.doxygen.org/) support. I'm not exactly sure how the integration would work. Something along the lines of a plugin to support .dox files would be my first thought. I'd leave generating the documentation from any source files for a separate run of Doxygen - it'd be easier and you probably don't want the source being edited over the web. diff --git a/doc/todo/else_parameter_for_map_plugin.mdwn b/doc/todo/else_parameter_for_map_plugin.mdwn index 50fe39357..12a91b4ee 100644 --- a/doc/todo/else_parameter_for_map_plugin.mdwn +++ b/doc/todo/else_parameter_for_map_plugin.mdwn @@ -14,14 +14,14 @@ documentation yet, I'm waiting for feedback first, but I'll do it for sure. -- [ >> Hmmm, what do you mean? Adding a syntax such as the one below? >> Or something else? - \[[if test="map(" then="..." else="..."]] + \[[!if test="map(" then="..." else="..."]] >> What would you write in the `then` clause? >> I'm not opposed at all to rewrite my two-liner, but I don't understand. >> --[[intrigeri]] - \[[if test="foo/*" then=""" - [[map pages="foo/*"]] + \[[!if test="foo/*" then=""" + [[!map pages="foo/*"]] """ else="no pages"]] --[[Joey]] diff --git a/doc/todo/enable-htaccess-files.mdwn b/doc/todo/enable-htaccess-files.mdwn index 4d377d3f6..b3c174fba 100644 --- a/doc/todo/enable-htaccess-files.mdwn +++ b/doc/todo/enable-htaccess-files.mdwn @@ -12,7 +12,7 @@ qr/(^|\/).svn\//, qr/.arch-ids\//, qr/{arch}\//], wiki_link_regexp => qr/\[\[(?:([^\]\|]+)\|)?([^\s\]#]+)(?:#([^\s\]]+))?\]\]/, -[[tag patch]] +[[!tag patch]] This lets the site administrator have a `.htaccess` file in their underlay directory, say, then get it copied over when the wiki is built. Without @@ -37,7 +37,7 @@ Hi, I would like to have my htaccess files in svn repository so ikiwiki would ex That way I have revision control on that file too. That may be a security concern, but I trust everybody that has svn commit access and such .htaccess files should not be accessible through wiki cgi. Of course, it could default to 'off'. -> See [[debbug 447267]] for a patch for this. +> See [[!debbug 447267]] for a patch for this. --- @@ -47,4 +47,4 @@ but I use ikiwiki with a very small group of people collaborating so svn/web acc and htaccess is for limiting access to some areas of wiki. It should be off by default of course. --Max -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/fileupload.mdwn b/doc/todo/fileupload.mdwn index 9a9106229..8c9b18b19 100644 --- a/doc/todo/fileupload.mdwn +++ b/doc/todo/fileupload.mdwn @@ -60,4 +60,4 @@ pagespec lock like the above prevents an edit or upload from happening, ikiwiki could display a reasonable message to the user, indicating what they've done wrong.) -[[tag soc done]] +[[!tag soc done]] diff --git a/doc/todo/fileupload/soc-proposal/discussion.mdwn b/doc/todo/fileupload/soc-proposal/discussion.mdwn index 1ce52f0ca..f85a956db 100644 --- a/doc/todo/fileupload/soc-proposal/discussion.mdwn +++ b/doc/todo/fileupload/soc-proposal/discussion.mdwn @@ -29,7 +29,7 @@ For images, videos, etc. it would be nice to have some kind of meta data file to height, compression, etc. which could be initially created by 'ikiwiki --generate-meta-stuff'. Then PageSpec should be teached to use these. Galleries could then be generated by means of -\[[inline pages="type(image/*) and year(2007)" template="gallery"]]. It +\[[!inline pages="type(image/*) and year(2007)" template="gallery"]]. It should of course be possible to edit this information via ikiwiki.cgi and with any text editor (Name: value). This should also allow for creations of default .html pages with the image/video/file/... and a discussion page. Probably named image.mdwn and image/discussion. diff --git a/doc/todo/format_escape.mdwn b/doc/todo/format_escape.mdwn index 45002f0c6..315b2d88f 100644 --- a/doc/todo/format_escape.mdwn +++ b/doc/todo/format_escape.mdwn @@ -97,7 +97,7 @@ I've created an updated [patch](http://www.idletheme.org/code/patches/ikiwiki-fo --Ryan Koppenhaver ## Original patch -[[tag patch]] +[[!tag patch]] <pre> Index: debian/changelog diff --git a/doc/todo/geotagging.mdwn b/doc/todo/geotagging.mdwn index 0f2514e0c..cb07e5e0c 100644 --- a/doc/todo/geotagging.mdwn +++ b/doc/todo/geotagging.mdwn @@ -2,4 +2,4 @@ Would be nice to see a way of geotagging pages in an ikiwiki, and search/sort pages by distance to a given location, as well as showing page locations on a map (Google Map, OpenStreetMap, etc). -- [[users/vibrog]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/git-rev-list_requires_relative_path___40__fixes_git_ctime__41__.mdwn b/doc/todo/git-rev-list_requires_relative_path___40__fixes_git_ctime__41__.mdwn index d811b8ea9..ec7d61b90 100644 --- a/doc/todo/git-rev-list_requires_relative_path___40__fixes_git_ctime__41__.mdwn +++ b/doc/todo/git-rev-list_requires_relative_path___40__fixes_git_ctime__41__.mdwn @@ -21,4 +21,4 @@ Better to strip the path out in getctime, I guess. --[[Joey]] -[[tag patch done]] +[[!tag patch done]] diff --git a/doc/todo/git_attribution.mdwn b/doc/todo/git_attribution.mdwn index ef59c221f..baa522adc 100644 --- a/doc/todo/git_attribution.mdwn +++ b/doc/todo/git_attribution.mdwn @@ -4,6 +4,6 @@ on the semantics you want to imply (does a web edit constitute a commit by the user or by the script?), it could also set `GIT_COMMITTER_NAME` and `GIT_COMMITTER_EMAIL` to the same values. --[[JoshTriplett]] -> See [[debbug 451023]] for a [[patch]] --[[Joey]] +> See [[!debbug 451023]] for a [[patch]] --[[Joey]] [[done]] diff --git a/doc/todo/graphviz.mdwn b/doc/todo/graphviz.mdwn index c55a4aa23..66ca0ae32 100644 --- a/doc/todo/graphviz.mdwn +++ b/doc/todo/graphviz.mdwn @@ -1,6 +1,6 @@ How about a plugin providing a [[preprocessor_directive|ikiwiki/preprocessordirective]] to render a -[[debpkg graphviz]] file as an image via one of the graphviz programs +[[!debpkg graphviz]] file as an image via one of the graphviz programs ("dot" by default) and include the resulting image on the page, using the "cmapx" image map format? graphviz files themselves could also render the same way into an HTML file with the same basename as the graphviz file; diff --git a/doc/todo/hard-coded_location_for_man_pages_and_w3m_cgi_wrapper.mdwn b/doc/todo/hard-coded_location_for_man_pages_and_w3m_cgi_wrapper.mdwn index 2ef231dde..a6a6ec1e1 100644 --- a/doc/todo/hard-coded_location_for_man_pages_and_w3m_cgi_wrapper.mdwn +++ b/doc/todo/hard-coded_location_for_man_pages_and_w3m_cgi_wrapper.mdwn @@ -12,7 +12,7 @@ while the default stays as it is now. > INSTALLMAN1DIR (though MakeMaker lacks one for man8). I'd prefer not > adding new variables where MakeMaker already has them. --[[Joey]] -[[tag patch]] +[[!tag patch]] <pre> diff --git a/doc/todo/index.html_allowed.mdwn b/doc/todo/index.html_allowed.mdwn index dabba6914..13ed49211 100644 --- a/doc/todo/index.html_allowed.mdwn +++ b/doc/todo/index.html_allowed.mdwn @@ -3,7 +3,7 @@ providing the usedirs option for output. The remaining patch, discussed below, concerns wanting to use foo/index.mdwn source files and get an output page name of foo, rather than foo/index. --[[Joey]] -[[tag patch]] +[[!tag patch]] --- diff --git a/doc/todo/language_definition_for_the_meta_plugin.mdwn b/doc/todo/language_definition_for_the_meta_plugin.mdwn index 2d1a56696..33098c601 100644 --- a/doc/todo/language_definition_for_the_meta_plugin.mdwn +++ b/doc/todo/language_definition_for_the_meta_plugin.mdwn @@ -1,5 +1,5 @@ Here is a patch for the [[plugins/meta]] plugin. It adds the possibility to define the language -used for a page, with \[[meta lang="ja"]] +used for a page, with \[[!meta lang="ja"]] It doesn't insert the langage information in the xhtml meta elements, but defines a LANG variable to use in the templates, for example with @@ -81,4 +81,4 @@ This may be useful for sites with a few pages in different languages, but no ful > Please resolve lang somewhere reusable rather than within meta plugin: It is certainly usable outside > the scope of the meta plugin as well. --[[JonasSmedegaard]] -[[tag wishlist patch plugins/meta translation]] +[[!tag wishlist patch plugins/meta translation]] diff --git a/doc/todo/latex.mdwn b/doc/todo/latex.mdwn index 01d927552..e96e4b782 100644 --- a/doc/todo/latex.mdwn +++ b/doc/todo/latex.mdwn @@ -1,7 +1,7 @@ How about a plugin adding a [[preprocessor_directive|ikiwiki/preprocessordirective]] to render some given LaTeX and include it in the page? This could either render the LaTeX as a PNG via -[[debpkg dvipng]] and include the resulting image in the page, or perhaps +[[!debpkg dvipng]] and include the resulting image in the page, or perhaps render via [HeVeA](http://pauillac.inria.fr/~maranget/hevea/index.html), [TeX2page](http://www.ccs.neu.edu/~dorai/tex2page/tex2page-doc.html), or similar. Useful for mathematics, as well as for stuff like the LaTeX version @@ -197,7 +197,7 @@ This are of course the minority of people (but I guess also the minority of peop > I'm thinking about renameing the preprocessor directive to teximg. -> \[[teximg code="" alt="foo"]] makes sense.. Would it make sense to rename +> \[[!teximg code="" alt="foo"]] makes sense.. Would it make sense to rename > the whole plugin, or do you think that other tex stuff should go in this > same plugin? @@ -216,5 +216,5 @@ Ah yes.. sorry forgot to update the plugin in my public_html folder %-). This wa > > --[[Joey]] -[[tag soc]] -[[tag wishlist]] +[[!tag soc]] +[[!tag wishlist]] diff --git a/doc/todo/let_inline_plugin_use_pagetemplates.mdwn b/doc/todo/let_inline_plugin_use_pagetemplates.mdwn index 94351fe5c..b220c8f6b 100644 --- a/doc/todo/let_inline_plugin_use_pagetemplates.mdwn +++ b/doc/todo/let_inline_plugin_use_pagetemplates.mdwn @@ -2,4 +2,4 @@ Is there any reason why the inline plugin's template parameter couldn't take any --[[madduck]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/limit_the_markup_formats_available_for_editing.mdwn b/doc/todo/limit_the_markup_formats_available_for_editing.mdwn index 7ac4c0771..c3eb09e52 100644 --- a/doc/todo/limit_the_markup_formats_available_for_editing.mdwn +++ b/doc/todo/limit_the_markup_formats_available_for_editing.mdwn @@ -5,4 +5,4 @@ For `aggregate` to work, I have to have the `html` plugin enabled, and this allo --[[madduck]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/meta_rcsid.mdwn b/doc/todo/meta_rcsid.mdwn index a09a48a64..81a2c1328 100644 --- a/doc/todo/meta_rcsid.mdwn +++ b/doc/todo/meta_rcsid.mdwn @@ -3,7 +3,7 @@ of CVS/SVN-style keywords (like '$Id$', etc.) from the source file in the page t > So the idea is you'd write something like: > -> \[[meta rcsid="$Id$"]] +> \[[!meta rcsid="$Id$"]] > > And this would be put at the bottom of the page or somewhere like that by > the template? diff --git a/doc/todo/metadata.mdwn b/doc/todo/metadata.mdwn index bf8191330..361f00351 100644 --- a/doc/todo/metadata.mdwn +++ b/doc/todo/metadata.mdwn @@ -1,7 +1,7 @@ There should be a way to add metadata to a page. Probably a plugin could do this, for example: - \[[meta foo="bar"]] + \[[!meta foo="bar"]] Uses for this include: @@ -11,9 +11,9 @@ Uses for this include: except it doesn't have to show up in the page text. * Recording page licenses. -[[meta link=done]] -[[meta title="supporting metadata..."]] -[[meta author="Joey Hess"]] -[[meta link="foo.css" rel="stylesheet" type="text/css"]] +[[!meta link=done]] +[[!meta title="supporting metadata..."]] +[[!meta author="Joey Hess"]] +[[!meta link="foo.css" rel="stylesheet" type="text/css"]] [[todo/done]] diff --git a/doc/todo/minor_adjustment_to_setup_documentation_for_recentchanges_feeds.mdwn b/doc/todo/minor_adjustment_to_setup_documentation_for_recentchanges_feeds.mdwn index fe47ab52f..c2dd5fbf4 100644 --- a/doc/todo/minor_adjustment_to_setup_documentation_for_recentchanges_feeds.mdwn +++ b/doc/todo/minor_adjustment_to_setup_documentation_for_recentchanges_feeds.mdwn @@ -18,7 +18,7 @@ turn on feeds for recentchanges. # Allow generating feeds even if not generated by default? #allowrss => 1, -[[tag patch]] +[[!tag patch]] > Hmm, recentchanges is just a blog. Of course the word "blog" is perhaps > being used in too broad a sense here, since it tends to imply personal diff --git a/doc/todo/missingparents.pm.mdwn b/doc/todo/missingparents.pm.mdwn index a85630ea3..0cc7137ba 100644 --- a/doc/todo/missingparents.pm.mdwn +++ b/doc/todo/missingparents.pm.mdwn @@ -4,9 +4,9 @@ has a child). Basically, you give it a page called missingparents.mdwn, something like this: <pre> -[[missingparents pages="posts/* and !posts/*/*" generate="""[[template id=year text="$page"]]"""]] -[[missingparents pages="posts/*/* and !posts/*/*/*" generate="""[[template id=month text="$page"]]"""]] -[[missingparents pages="posts/*/*/* and !posts/*/*/*/*" generate="""[[template id=day text="$page"]]"""]] +[[!missingparents pages="posts/* and !posts/*/*" generate="""[[!template id=year text="$page"]]"""]] +[[!missingparents pages="posts/*/* and !posts/*/*/*" generate="""[[!template id=month text="$page"]]"""]] +[[!missingparents pages="posts/*/*/* and !posts/*/*/*/*" generate="""[[!template id=day text="$page"]]"""]] </pre> And it scans the whole wiki for pages that match the pagespecs but are missing @@ -105,7 +105,7 @@ Index: IkiWiki/Plugin/missingparents.pm + my %params=@_; + + if (! defined $params{pages} || ! defined $params{generate}) { -+ return "[[missingparents ".gettext("missing pages or generate parameter")."]]"; ++ return "[[!missingparents ".gettext("missing pages or generate parameter")."]]"; + } + + push @pagespecs, \%params; @@ -258,4 +258,4 @@ Index: IkiWiki.pm my $page=shift; </pre> -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/more_class__61____34____34___for_css.mdwn b/doc/todo/more_class__61____34____34___for_css.mdwn index ea914e9ed..4712c12b3 100644 --- a/doc/todo/more_class__61____34____34___for_css.mdwn +++ b/doc/todo/more_class__61____34____34___for_css.mdwn @@ -36,7 +36,7 @@ added after an inlined page (namely: the post date, the tags, and the actions): + +</div> -[[tag patch]] +[[!tag patch]] > Unfortunately, the inlinepage content passes through markdown, and markdown > gets confused by these nested div's and puts p's around one of them, generating @@ -53,7 +53,7 @@ added after an inlined page (namely: the post date, the tags, and the actions): >> alternatives is always a good thing and perhaps, the fact that pandoc can make markdown->LaTeX >> conversion may lead to new possibilities. --[[Roktas]] ->>> I confirm that this ([[debbug 405058]]) has just been fixed in markdown +>>> I confirm that this ([[!debbug 405058]]) has just been fixed in markdown >>> [`1.0.2b7`](http://packages.debian.org/experimental/web/markdown) (BTW, thanks to your bug >>> report Joey). FYI, I've observed some performance drop with `1.0.2b7` compared to `1.0.1`, >>> especially noticable with big files. This was also confirmed by someone else, for example, diff --git a/doc/todo/multiple_output_formats.mdwn b/doc/todo/multiple_output_formats.mdwn index 00623be39..0538f894c 100644 --- a/doc/todo/multiple_output_formats.mdwn +++ b/doc/todo/multiple_output_formats.mdwn @@ -14,4 +14,4 @@ would be impractical to say the least. --[[bma]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/multiple_repository_support.mdwn b/doc/todo/multiple_repository_support.mdwn index 33d794790..0625dba7e 100644 --- a/doc/todo/multiple_repository_support.mdwn +++ b/doc/todo/multiple_repository_support.mdwn @@ -12,4 +12,4 @@ manually configure it in the setup file. --[[Joey]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/nested_preprocessor_directives.mdwn b/doc/todo/nested_preprocessor_directives.mdwn index 7e7ef3a49..b5080dc3c 100644 --- a/doc/todo/nested_preprocessor_directives.mdwn +++ b/doc/todo/nested_preprocessor_directives.mdwn @@ -11,8 +11,8 @@ nesting, a new syntax would be needed. Maybe something xml-like? > > For example, I *think* you can unambiguously parse the following: > -> \[[if test="enabled(template) and templates/foo" then=""" -> [[template id=foo content="""Flying Purple People Eater"""]] +> \[[!if test="enabled(template) and templates/foo" then=""" +> [[!template id=foo content="""Flying Purple People Eater"""]] > """]] > > --[[JoshTriplett]] diff --git a/doc/todo/pagespec_relative_to_a_target.mdwn b/doc/todo/pagespec_relative_to_a_target.mdwn index 62bb3ea29..f7b248670 100644 --- a/doc/todo/pagespec_relative_to_a_target.mdwn +++ b/doc/todo/pagespec_relative_to_a_target.mdwn @@ -88,7 +88,7 @@ diff -urNX ignorepats ikiwiki/IkiWiki/Plugin/relative.pm ikidev/IkiWiki/Plugin/r +1 </pre> -[[tag patch]] +[[!tag patch]] > This looks really interesting. It reminds me of XPath and its conditionals. > Those might actually work well adapted to pagespecs. For instance, to write diff --git a/doc/todo/parse_debian_packages.mdwn b/doc/todo/parse_debian_packages.mdwn index 266686605..2425645d9 100644 --- a/doc/todo/parse_debian_packages.mdwn +++ b/doc/todo/parse_debian_packages.mdwn @@ -67,4 +67,4 @@ automatically. >>> Sure, a plugin is just a perl library so can easily be packaged >>> separately. -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/passwordauth:_sendmail_interface.mdwn b/doc/todo/passwordauth:_sendmail_interface.mdwn index 4bbda6565..9598af234 100644 --- a/doc/todo/passwordauth:_sendmail_interface.mdwn +++ b/doc/todo/passwordauth:_sendmail_interface.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist]] For sending out password reminder emails, the [[plugins/passwordauth]] plugin currently uses the *[Mail::Sendmail](http://search.cpan.org/perldoc?Mail::Sendmail)* module. @@ -24,7 +24,7 @@ in the ikiwiki source code, where emailing is done. --[[tschwinge]] -> One that is in Debian is [[cpan Email::Send]], which can do SMTP and +> One that is in Debian is [[!cpan Email::Send]], which can do SMTP and > sendmail and some other methods and falls back through methods until one > succeeds. I haven't tried to use it but it looks like a feasable > candidate. @@ -34,13 +34,13 @@ in the ikiwiki source code, where emailing is done. OK, so I'll have a look at replacing all email handling with *Email::Send*. -[[tag patch]] +[[!tag patch]] *<http://www.thomas.schwinge.homeip.net/tmp/ikiwiki-sendmail.patch>* Remaining TODOs: * Resolve TODOs as denoted inside the patch. - * Is it worthwhile to use and depend on [[cpan Return::Value]] + * Is it worthwhile to use and depend on [[!cpan Return::Value]] just for this bit of functionality? * Debian news file. * ikiwiki news file. diff --git a/doc/todo/pedigree_plugin.mdwn b/doc/todo/pedigree_plugin.mdwn index 2839659f4..1977c3d4d 100644 --- a/doc/todo/pedigree_plugin.mdwn +++ b/doc/todo/pedigree_plugin.mdwn @@ -191,4 +191,4 @@ Merged, nice work. (Overkill having a test suite. ;-) --[[Joey]] > (master language + translations) support. Expect news from me on > this front in the next weeks. --[[intrigeri]] -[[tag patch done]] +[[!tag patch done]] diff --git a/doc/todo/preprocessor_directive_for_proposed_changes.mdwn b/doc/todo/preprocessor_directive_for_proposed_changes.mdwn index e73e6c09e..c0af59eba 100644 --- a/doc/todo/preprocessor_directive_for_proposed_changes.mdwn +++ b/doc/todo/preprocessor_directive_for_proposed_changes.mdwn @@ -10,11 +10,11 @@ and wait for someone with the access/confidence to apply them. Maybe this can be enhanced with a [[ikiwiki/PreprocessorDirective]]: <pre> -\[[suggest op=merge dstfile=trunk srcfile=branches/jk oldrev=1234 newrev=1342]] +\[[!suggest op=merge dstfile=trunk srcfile=branches/jk oldrev=1234 newrev=1342]] -\[[suggest op=move srcpage=/blog dstpage=/blog_support]] +\[[!suggest op=move srcpage=/blog dstpage=/blog_support]] -\[[suggest patch=""" +\[[!suggest patch=""" Index: IkiWiki/CGI.pm =================================================================== --- IkiWiki/CGI.pm (révision 4119) diff --git a/doc/todo/provide_a_mailing_list.mdwn b/doc/todo/provide_a_mailing_list.mdwn index f34ed77c6..6e0cd51e6 100644 --- a/doc/todo/provide_a_mailing_list.mdwn +++ b/doc/todo/provide_a_mailing_list.mdwn @@ -37,4 +37,4 @@ more users, the number of such requests will also increase. --[[madduck]] >> can use that as an alternative. I'm happy to chat about this, ping me.. >> --[sm](http://joyful.com) -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/provide_inline_diffs_in_recentchanges.mdwn b/doc/todo/provide_inline_diffs_in_recentchanges.mdwn index 43700337d..7724576f5 100644 --- a/doc/todo/provide_inline_diffs_in_recentchanges.mdwn +++ b/doc/todo/provide_inline_diffs_in_recentchanges.mdwn @@ -1,3 +1,3 @@ It would rock if I could view diffs from the web without going via feeds. I envision toggle-style buttons on the recentchanges page, or just links to the CGI, which then displays the diff... --[[madduck]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/quieten-bzr.mdwn b/doc/todo/quieten-bzr.mdwn index 11ce139b4..c6d83a519 100644 --- a/doc/todo/quieten-bzr.mdwn +++ b/doc/todo/quieten-bzr.mdwn @@ -20,7 +20,7 @@ The fix is simply to call `bzr` with the _--quiet_ switch. Something like this a > -[[tag patch]] +[[!tag patch]] > [[done]], although I left off the escapeHTML thing which seems to be in > your patch by accident. diff --git a/doc/todo/rcs.mdwn b/doc/todo/rcs.mdwn index 3793f7533..3cc572516 100644 --- a/doc/todo/rcs.mdwn +++ b/doc/todo/rcs.mdwn @@ -3,7 +3,7 @@ I have used it probably over hundred times but needs some work. <http://www.reedmedia.net/~reed/tmp-sfhkcjkfrfh/rcs.pm> -[[tag patch]] +[[!tag patch]] > Clearly needs some cleanup and perhaps some of the missing stubs > implemented, before it can be included into ikiwiki. diff --git a/doc/todo/recentchanges.mdwn b/doc/todo/recentchanges.mdwn index 91128a860..25a8ea4db 100644 --- a/doc/todo/recentchanges.mdwn +++ b/doc/todo/recentchanges.mdwn @@ -92,7 +92,7 @@ your pages. --Ethan Here's a full design for redoing recentchanges, based on Ethan's ideas: * Add a recentchanges plugin that has a preprocessor directive: - \[[recentchanges num=100 pages=* template=recentchanges.tmpl]] + \[[!recentchanges num=100 pages=* template=recentchanges.tmpl]] If put on the [[recentchanges]] page, this would result in up to 100 recentchanges/change_$id.mdwn files being created. * Which means the plugin has to store state and use a checkconfig hook diff --git a/doc/todo/rel_attribute_for_links.mdwn b/doc/todo/rel_attribute_for_links.mdwn index 331721b55..3b4cea436 100644 --- a/doc/todo/rel_attribute_for_links.mdwn +++ b/doc/todo/rel_attribute_for_links.mdwn @@ -16,4 +16,4 @@ This can also help for css decoraton. An example of these patches in use: http:/ — NicolasLimare -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn index c73b53e53..dfeacbabd 100644 --- a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn +++ b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist]] HTML::Template is an okay templating kit, but it lacks a lot of powerful features and thus makes it rather hard to give an ikiwiki site a consistent diff --git a/doc/todo/review_mechanism.mdwn b/doc/todo/review_mechanism.mdwn index 5e4ba212e..66ed58144 100644 --- a/doc/todo/review_mechanism.mdwn +++ b/doc/todo/review_mechanism.mdwn @@ -32,4 +32,4 @@ Change queues would be wiki pages as well (probably using [[inlines|plugins/inli > > -- [[JoshTriplett]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/shortcut_link_text.mdwn b/doc/todo/shortcut_link_text.mdwn index d03d37411..765c445ab 100644 --- a/doc/todo/shortcut_link_text.mdwn +++ b/doc/todo/shortcut_link_text.mdwn @@ -1,19 +1,19 @@ [[plugins/shortcut]] creates link shortcut [[ikiwiki/PreprocessorDirective]]s, which substitute their argument into the specified shortcut URL to generate the link target, and use the argument as the link text. For example, given -the example [[shortcuts]], `\[[wikipedia ikiwiki]]` generates a link to +the example [[shortcuts]], `\[[!wikipedia ikiwiki]]` generates a link to <http://en.wikipedia.org/wiki/ikiwiki>, with the link text "ikiwiki". This works well in many cases; however, for things like the `debbug` example, it simply uses the number as the link text, which does not always provide enough context to understand the link at first glance. For example, -`\[[debbug 397501]]` generates a link to <http://bugs.debian.org/397501>, +`\[[!debbug 397501]]` generates a link to <http://bugs.debian.org/397501>, with just "397501" as the link text. While [[plugins/template]] provides a general solution for arbitrary cases, it would help to have a simple option via the shortcut plugin to set the link text, with a `%s` substitution. -Thus, something like `\[[shortcut name=debbug +Thus, something like `\[[!shortcut name=debbug url="http://bugs.debian.org/%s" desc="bug #%s"]]` might suffice on a Debian-specific wiki to indicate a bug number, while a more general wiki -might use something like `\[[shortcut name=debbug +might use something like `\[[!shortcut name=debbug url="http://bugs.debian.org/%s" desc="Debian bug #%s"]]`. > [[todo/done]] --[[Joey]] diff --git a/doc/todo/shortcut_optional_parameters.mdwn b/doc/todo/shortcut_optional_parameters.mdwn index daec3696a..445404315 100644 --- a/doc/todo/shortcut_optional_parameters.mdwn +++ b/doc/todo/shortcut_optional_parameters.mdwn @@ -6,39 +6,39 @@ Consider the "All files in this package search" on To create a "debfiles" [[shortcut|shortcuts]] that takes a package name, you could just hardcode the architecture and distribution: - \[[shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=unstable&arch=i386"]] - \[[debfiles ikiwiki]] + \[[!shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=unstable&arch=i386"]] + \[[!debfiles ikiwiki]] But what if you could have them as optional parameters instead? The syntax for the invocation should look like this: - \[[debfiles ikiwiki dist=testing]] + \[[!debfiles ikiwiki dist=testing]] Some possible syntax choices for the shortcut definition: - \[[shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%(dist)s&arch=%(arch)s" dist="unstable" arch="i386"]] - \[[shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%(dist=unstable)s&arch=%(arch=i386)s"]] - \[[shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%{dist=unstable}&arch=%{arch=i386}"]] - \[[shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=$*&searchmode=filelist&case=insensitive&version=${dist=unstable}&arch=${arch=i386}"]] + \[[!shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%(dist)s&arch=%(arch)s" dist="unstable" arch="i386"]] + \[[!shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%(dist=unstable)s&arch=%(arch=i386)s"]] + \[[!shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=%s&searchmode=filelist&case=insensitive&version=%{dist=unstable}&arch=%{arch=i386}"]] + \[[!shortcut name=debfiles url="http://packages.debian.org/cgi-bin/search_contents.pl?word=$*&searchmode=filelist&case=insensitive&version=${dist=unstable}&arch=${arch=i386}"]] --[[JoshTriplett]] Well, you can already do this kind of thing with templates. Invocation does look different: - \[[template id=debfiles package=ikiwiki dist=testing]] + \[[!template id=debfiles package=ikiwiki dist=testing]] --[[Joey]] > I think I would find templates sufficient, if: > > 1. I could use the name of the template as a preprocessor directive -> (`\[[templatename ...]]`), rather than using the `template` directive -> with an `id` argument (`\[[template id=templatename]]`). +> (`\[[!templatename ...]]`), rather than using the `template` directive +> with an `id` argument (`\[[!template id=templatename]]`). > 2. Template invocation allowed bare values in addition to `key=value` > arguments, and template definition supported some means to access the -> value. This would allow `\[[debfiles ikiwiki]]` rather than -> `\[[debfiles package=ikiwiki]]`. +> value. This would allow `\[[!debfiles ikiwiki]]` rather than +> `\[[!debfiles package=ikiwiki]]`. > 3. I could use ikiwiki syntax in the template, not just HTML and > HTML::Template. (If I can already do that, then [[/plugins/template]] > should make that more clear.) diff --git a/doc/todo/shortcut_with_different_link_text.mdwn b/doc/todo/shortcut_with_different_link_text.mdwn index 93f9651a4..8615b2754 100644 --- a/doc/todo/shortcut_with_different_link_text.mdwn +++ b/doc/todo/shortcut_with_different_link_text.mdwn @@ -11,7 +11,7 @@ Window System protocol". --[[JoshTriplett]] > If I don't understand this, can you give an HTML example? --[[JeremyReed]] >> The problem is like that in [[bugs/shortcuts_don't_escape_from_Markdown]]. We would like to use ->> the shortcuts plugin but add a descriptive text -- in this case \[[xcbgit src/xcb.xsd|XML Schema...]] +>> the shortcuts plugin but add a descriptive text -- in this case \[[!xcbgit src/xcb.xsd|XML Schema...]] >> The file src/xcb.xsd could be any url, and the point of shortcuts is that you get to shorten it. >> --Ethan @@ -22,7 +22,7 @@ Window System protocol". --[[JoshTriplett]] >>> However, I want to define a [[plugins/shortcut]] to save the typing. If I >>> define something like `protogit` pointing to >>> `http://gitweb.freedesktop.org/?p=xcb/proto.git;a=blob;hb=HEAD;f=%s`, then ->>> I can write `\[[protogit src/xcb.xsd]]`; however, I then can't change the +>>> I can write `\[[!protogit src/xcb.xsd]]`; however, I then can't change the >>> link text to anything other than what the shortcut defines as the link >>> text. I want to write something like >>> `\[[XML Schema for the X Window System Protocol|protogit src/xcb.xsd]]`, @@ -44,22 +44,22 @@ Window System protocol". --[[JoshTriplett]] --- -One possible alternative, would be a general `\[[url ]]` scheme for all kinds of links. As mentioned in [[Short_wikilinks]], I have wanted a way to enter links to the wiki with markdown-style references, +One possible alternative, would be a general `\[[!url ]]` scheme for all kinds of links. As mentioned in [[Short_wikilinks]], I have wanted a way to enter links to the wiki with markdown-style references, specifying the actual target elsewhere from the text, with just a short reference in the text. To facilitate automatic conversion from earlier (already markdownised) "blog", I finally ended up writing a custom plugin that simply gets the location of wikipage, and use markdown mechanisms: Here [is][1] a link. - [1]: [[l a_page_in_the_wiki]] + [1]: [[!l a_page_in_the_wiki]] - Obviously [this]([[l another_page]]) also works, although the syntax is quite cumbersome. + Obviously [this]([[!l another_page]]) also works, although the syntax is quite cumbersome. So that the 'l' plugin inserts the location the page there, and markdown does the rest. My plugin currently fails if it can't find the page, as that is sufficient for my needs. Differing colouring for non-existing pages is not doable in a straightforward manner with this approach. -For external links, that is no concern, however. So you could define for each shortcut an alternative directive, that inserts the URL. Perhaps `\[[url shortcutname params]]` or `\[[@shortcutname params]]` (if the preprocessor supported the @), and this could be extended to local links in an obvious manner: `\[[url page]]` or `\[[@page]]`. Now, if you could just get rid off the parantheses for markdown, for the short inline links --[[tuomov]] (who'd really rather not have two separate linking mechanisms: ikiwiki's heavy syntax and markdown's lighter one). +For external links, that is no concern, however. So you could define for each shortcut an alternative directive, that inserts the URL. Perhaps `\[[!url shortcutname params]]` or `\[[@shortcutname params]]` (if the preprocessor supported the @), and this could be extended to local links in an obvious manner: `\[[!url page]]` or `\[[@page]]`. Now, if you could just get rid off the parantheses for markdown, for the short inline links --[[tuomov]] (who'd really rather not have two separate linking mechanisms: ikiwiki's heavy syntax and markdown's lighter one). --- -I've added code to make the \[[foo 123]] syntax accept a _desc_ +I've added code to make the \[[!foo 123]] syntax accept a _desc_ parameter. I've named it like this to signal that it overrides the _desc_ provided at description time. `%s` is expanded here as well. diff --git a/doc/todo/shortcut_with_no_url_parameter__44___only_desc.mdwn b/doc/todo/shortcut_with_no_url_parameter__44___only_desc.mdwn index c8e138820..56a74029e 100644 --- a/doc/todo/shortcut_with_no_url_parameter__44___only_desc.mdwn +++ b/doc/todo/shortcut_with_no_url_parameter__44___only_desc.mdwn @@ -16,8 +16,8 @@ It sounds like you're looking for templates, not shortcuts. --[[Joey]] > `url` still seems reasonable, and simple. You could also use such shortcuts > without markup at all, as an abbreviation mechanism: > -> \[[shortcut name=spi desc="Software in the Public Interest, Inc."]]]. -> \[[shortcut name=sosp desc="Symposium on Operating System Principles"]]]. -> \[[shortcut name=cacm desc="Communications of the ACM"]]]. +> \[[!shortcut name=spi desc="Software in the Public Interest, Inc."]]]. +> \[[!shortcut name=sosp desc="Symposium on Operating System Principles"]]]. +> \[[!shortcut name=cacm desc="Communications of the ACM"]]]. > > --[[JoshTriplett]] diff --git a/doc/todo/should_optimise_pagespecs.mdwn b/doc/todo/should_optimise_pagespecs.mdwn index 980435111..0ef8a7847 100644 --- a/doc/todo/should_optimise_pagespecs.mdwn +++ b/doc/todo/should_optimise_pagespecs.mdwn @@ -18,8 +18,8 @@ Couldn't isolate the cause, but some sources for this problem may be: Other special things in my templates and site: -* a sidebar with \[[include pages="notes/\*" template=foo]] while notes.mdwn has - a \[[include pages="notes/*"]] and uses the sidebar; removed it, doesn't change +* a sidebar with \[[!include pages="notes/\*" template=foo]] while notes.mdwn has + a \[[!include pages="notes/*"]] and uses the sidebar; removed it, doesn't change * a template (biblio.tmpl) calling the "img" plugin with a template parameter as the image filename; removed it, doesn't change * some strange games with tags whose page calls a "map" directive to show other tags @@ -79,4 +79,4 @@ I can think about reducung the size of my wiki source and making it available on > > --[[Joey]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/simple_text_parsing_or_regex_in_template_or_shortcut.mdwn b/doc/todo/simple_text_parsing_or_regex_in_template_or_shortcut.mdwn index 7b3dbbd55..3ff8b9ef6 100644 --- a/doc/todo/simple_text_parsing_or_regex_in_template_or_shortcut.mdwn +++ b/doc/todo/simple_text_parsing_or_regex_in_template_or_shortcut.mdwn @@ -2,8 +2,8 @@ Either [[plugins/template]] or [[plugins/shortcut]] should support some form of very simple text parsing or regex application, to make it possible to write shortcuts like these: - [[mmlist listname@lists.example.org]] -> <listname@example.org> ([mailman page] (http://lists.example.org/mailman/listinfo/listname) - [[debcl packagename]] -> [packagename changelog](http://packages.debian.org/changelogs/pool/main/p/packagename/current/changelog) + [[!mmlist listname@lists.example.org]] -> <listname@example.org> ([mailman page] (http://lists.example.org/mailman/listinfo/listname) + [[!debcl packagename]] -> [packagename changelog](http://packages.debian.org/changelogs/pool/main/p/packagename/current/changelog) For shortcut definitions, a `match` parameter could supply a regex, and then the `url` and `desc` parameters could make use of the named or numbered groups from the match. diff --git a/doc/todo/skip_option_for_inline_plugin.mdwn b/doc/todo/skip_option_for_inline_plugin.mdwn index 06f1a8358..f37d75ccb 100644 --- a/doc/todo/skip_option_for_inline_plugin.mdwn +++ b/doc/todo/skip_option_for_inline_plugin.mdwn @@ -1,7 +1,7 @@ How about a skip option for [[plugins/inline]]? This would allow things like the following: - \[[inline pages="news/*" show="5"]] - \[[inline pages="news/*" skip="5" show="5" archive="yes"]] + \[[!inline pages="news/*" show="5"]] + \[[!inline pages="news/*" skip="5" show="5" archive="yes"]] > I just wrote a patch. --Ethan diff --git a/doc/todo/stylesheet_suggestion_for_verbatim_content.mdwn b/doc/todo/stylesheet_suggestion_for_verbatim_content.mdwn index 51a409963..b73155c98 100644 --- a/doc/todo/stylesheet_suggestion_for_verbatim_content.mdwn +++ b/doc/todo/stylesheet_suggestion_for_verbatim_content.mdwn @@ -7,7 +7,7 @@ AFAICS, my web browser already has a built-in monospace font, which I can see in action in the preformatted patch below. So I don't see why the default style sheet should do this. --[[Joey]] -[[tag patch]] +[[!tag patch]] <pre> diff --git a/basewiki/style.css b/basewiki/style.css diff --git a/doc/todo/support_for_SDF_documents.mdwn b/doc/todo/support_for_SDF_documents.mdwn index a59f9ad5a..18ce4e106 100644 --- a/doc/todo/support_for_SDF_documents.mdwn +++ b/doc/todo/support_for_SDF_documents.mdwn @@ -1,8 +1,8 @@ -I think it would be useful for ikiwiki to support [[debpkg sdf]] input, +I think it would be useful for ikiwiki to support [[!debpkg sdf]] input, which can be converted and rendered to many formats. I should add, however, that SDF allows executing arbitrary perl code from its documents; which means some sanitization would need to occur before the document is fed to sdf. --[[JeremieKoenig]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/supporting_comments_via_disussion_pages.mdwn b/doc/todo/supporting_comments_via_disussion_pages.mdwn index 50bc17ba3..14a8b3f71 100644 --- a/doc/todo/supporting_comments_via_disussion_pages.mdwn +++ b/doc/todo/supporting_comments_via_disussion_pages.mdwn @@ -62,7 +62,7 @@ So, I have some code, included below. For some reason that I don't quite get it What I ended up doing is write something like this to the page: - [[blogcomment from="""Username""" timestamp="""12345""" subject="""Some text""" text="""the text of the comment"""]] + [[!blogcomment from="""Username""" timestamp="""12345""" subject="""Some text""" text="""the text of the comment"""]] Each comment is processed to something like this: @@ -133,7 +133,7 @@ Each comment is processed to something like this: $cgi->param('comments') : ''; my $comment=$cgi->param('blogcomment'); - $content.=qq{[[blogcomment from="""$name""" timestamp="""$timestamp""" subject="""$subject""" text="""$comment"""]]\n\n}; + $content.=qq{[[!blogcomment from="""$name""" timestamp="""$timestamp""" subject="""$subject""" text="""$comment"""]]\n\n}; $content=~s/\n/\r\n/g; $form->field(name => "editcontent", value => $content, force => 1); } # }}} diff --git a/doc/todo/tidy_git__39__s_ctime_debug_output.mdwn b/doc/todo/tidy_git__39__s_ctime_debug_output.mdwn index 6820be5cc..aaa040ec7 100644 --- a/doc/todo/tidy_git__39__s_ctime_debug_output.mdwn +++ b/doc/todo/tidy_git__39__s_ctime_debug_output.mdwn @@ -12,4 +12,4 @@ return $ctime; } #}}} -[[tag patch done]] +[[!tag patch done]] diff --git a/doc/todo/tla.mdwn b/doc/todo/tla.mdwn index f78d08b44..6ef8453f1 100644 --- a/doc/todo/tla.mdwn +++ b/doc/todo/tla.mdwn @@ -1,4 +1,4 @@ * Need to get post commit hook code working. * Need some example urls for web based diffs. -[[tag rcs/tla]] +[[!tag rcs/tla]] diff --git a/doc/todo/tmplvars_plugin.mdwn b/doc/todo/tmplvars_plugin.mdwn index 33d161ee1..fe163fb5f 100644 --- a/doc/todo/tmplvars_plugin.mdwn +++ b/doc/todo/tmplvars_plugin.mdwn @@ -1,6 +1,6 @@ A simple plugin to allow per-page customization of a template by passing paramaters to HTML::Template. For those times when a whole pagetemplate is too much work. --Ethan -[[tags patch]] +[[!tags patch]] #!/usr/bin/perl package IkiWiki::Plugin::tmplvars; diff --git a/doc/todo/toc_plugin_to_skip_one_level.mdwn b/doc/todo/toc_plugin_to_skip_one_level.mdwn index 35290fc38..4891a1197 100644 --- a/doc/todo/toc_plugin_to_skip_one_level.mdwn +++ b/doc/todo/toc_plugin_to_skip_one_level.mdwn @@ -1,6 +1,6 @@ It would be great if I could to this: - \[[toc levels=3 skip=1]] + \[[!toc levels=3 skip=1]] I use h1 for big title on each page, and don't want it in my toc on that page. @@ -10,7 +10,7 @@ That way I could have toc for h2 and h3 and h1 is skipped bacause it is big titl > another option is added, I wonder why you're using a h1 for a title on > each page when the page name already appears at the top of each page. And > if the page name isn't right for the title, you can use -> \[[meta title="foo"]] to override it. And this purposefully doesn't show +> \[[!meta title="foo"]] to override it. And this purposefully doesn't show > up in the toc. --[[Joey]] >> aaaahhh, I made a mistake. U used some other page.tmpl and title was hidden, diff --git a/doc/todo/toggle_initial_state.mdwn b/doc/todo/toggle_initial_state.mdwn index cbbf7e6fd..f7b684b51 100644 --- a/doc/todo/toggle_initial_state.mdwn +++ b/doc/todo/toggle_initial_state.mdwn @@ -1,6 +1,6 @@ It would be nice if one could set the initial state of the toggleable area. --[[[rdennis]] -[[tag plugins/toggle]] +[[!tag plugins/toggle]] [[done]] diff --git a/doc/todo/turn_edittemplate_verbosity_off_by_default.mdwn b/doc/todo/turn_edittemplate_verbosity_off_by_default.mdwn index 8b6941310..4c703b940 100644 --- a/doc/todo/turn_edittemplate_verbosity_off_by_default.mdwn +++ b/doc/todo/turn_edittemplate_verbosity_off_by_default.mdwn @@ -27,4 +27,4 @@ I think this (untested) patch might just do the trick: --[[madduck]] -[[tags wishlist patch]] +[[!tags wishlist patch]] diff --git a/doc/todo/typography_plugin_configuration.mdwn b/doc/todo/typography_plugin_configuration.mdwn index 91ac4ba85..dd162a084 100644 --- a/doc/todo/typography_plugin_configuration.mdwn +++ b/doc/todo/typography_plugin_configuration.mdwn @@ -1,5 +1,5 @@ The [[typography_plugin|plugins/typography]] could support configuration of -which translations to make. [[cpan Text::Typography]] supports fine-grained +which translations to make. [[!cpan Text::Typography]] supports fine-grained control of which translations to make, so [[plugins/typography]] just needs to expose this somehow. --[[JoshTriplett]] diff --git a/doc/todo/unaccent_url_instead_of_encoding.mdwn b/doc/todo/unaccent_url_instead_of_encoding.mdwn index fbba893c5..1be150a82 100644 --- a/doc/todo/unaccent_url_instead_of_encoding.mdwn +++ b/doc/todo/unaccent_url_instead_of_encoding.mdwn @@ -6,4 +6,4 @@ This is a one liner change, but requires a bit of reordering in the code. [[cstamas]] -[[tag wishlist patch]] +[[!tag wishlist patch]] diff --git a/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn b/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn index c5fe28f4b..492a32b36 100644 --- a/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn +++ b/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn @@ -15,7 +15,7 @@ ManojSrivastava > I think you could now implement "toplvl" using [[conditionals|/plugins/conditional]]: > -> \[[if test="destpage(/index)" then="""...""" else="""..."""]] +> \[[!if test="destpage(/index)" then="""...""" else="""..."""]] > > --[[JoshTriplett]] @@ -263,4 +263,4 @@ ManojSrivastava + </pre> -[[tag patch]] +[[!tag patch]] diff --git a/doc/todo/web_gui_for_managing_tags.mdwn b/doc/todo/web_gui_for_managing_tags.mdwn index 3dd59f162..c865bf738 100644 --- a/doc/todo/web_gui_for_managing_tags.mdwn +++ b/doc/todo/web_gui_for_managing_tags.mdwn @@ -9,4 +9,4 @@ MoinMoin has a simple implementation of this, [click here to see an example](htt --[[AdamShand]] -[[tag wishlist]] +[[!tag wishlist]] diff --git a/doc/todo/wikiwyg.mdwn b/doc/todo/wikiwyg.mdwn index f2af47e27..e3d1b3927 100644 --- a/doc/todo/wikiwyg.mdwn +++ b/doc/todo/wikiwyg.mdwn @@ -22,11 +22,11 @@ other way to feed it the actual source for a page, this seems like a problem. According to the developers, it is possible to do that, and start off in WikiText mode. -[[tag soc]] +[[!tag soc]] -[[tag wishlist]] +[[!tag wishlist]] -[[tag patch]] +[[!tag patch]] Project IkiWiki::WIKIWYG v1.6 - <http://ikiwiki.xbaud.com/> =========================================================== |