Merge branch 'master' of ssh://git.ikiwiki.info
commit
53bf8ec710
|
@ -0,0 +1,8 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="https://www.google.com/accounts/o8/id?id=AItOawlcaGfdn9Kye1Gc8aGb67PDVQW4mKbQD7E"
|
||||||
|
nickname="Amitai"
|
||||||
|
subject="comment 2"
|
||||||
|
date="2013-11-05T19:18:10Z"
|
||||||
|
content="""
|
||||||
|
What version of ikiwiki are you running? [[news/Version 3.20130904]] introduced some changes to the RSS and Atom templates that may help you.
|
||||||
|
"""]]
|
|
@ -0,0 +1,8 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="https://tincho.startssl.com/"
|
||||||
|
nickname="tincho"
|
||||||
|
subject="comment 3"
|
||||||
|
date="2013-11-05T19:35:45Z"
|
||||||
|
content="""
|
||||||
|
I am using the same version as you say. And the entry template has a place for author that does not get populated. The page template does not, on the other hand.
|
||||||
|
"""]]
|
|
@ -0,0 +1,8 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="https://www.google.com/accounts/o8/id?id=AItOawlUQVv1tLm_aWTKoX36OqxUUkyowomdt4E"
|
||||||
|
nickname="Meng"
|
||||||
|
subject="recipe"
|
||||||
|
date="2013-11-06T07:50:24Z"
|
||||||
|
content="""
|
||||||
|
SO has a thread on this: http://stackoverflow.com/questions/6889564/add-mathjax-support-to-a-local-ikiwiki .
|
||||||
|
"""]]
|
|
@ -0,0 +1 @@
|
||||||
|
Thanks, good stuff. I wrote something similar to facilitate delaying the publication of pages until after a certain date, but mine is quite rough and ready. — [[Jon]]
|
|
@ -0,0 +1,28 @@
|
||||||
|
# Syntax highlighting of recent changes
|
||||||
|
|
||||||
|
Hello,
|
||||||
|
is there a simple way to highlight the diff printed in the [[/recentchanges]]
|
||||||
|
page? I imagined several solutions, but I am still wondering about the best one.
|
||||||
|
|
||||||
|
* One might activate the [[plugins/highlight]] and [[plugins/format]] plugins,
|
||||||
|
and change the [[change.tmpl|/templates]] template, to use this plugin. But as
|
||||||
|
the diff is formatted not to mess up html (e.g. `\[[link]]` becomes
|
||||||
|
`[[link]]`), the output would be unreadable.
|
||||||
|
* One might improve [[plugins/recentchangesdiff]] plugin by adding an option
|
||||||
|
`diff_escape_html=>yes/no` to it. Setting this to `no` would leave html
|
||||||
|
unescaped, so that it would be correctly rendered by plugin
|
||||||
|
[[plugins/format]].
|
||||||
|
* One might change the [[plugins/recentchangesdiff]] plugin, to add syntax
|
||||||
|
highlighting to diffs, but this would duplicate plugin [[plugins/highlight]].
|
||||||
|
|
||||||
|
In my opinion, the second solution is the best one. However, to be neat the
|
||||||
|
`change.tmpl` template might detect that both plugin [[plugins/format]] and
|
||||||
|
`diff_escape_html` option are enabled, and, depending on it, output the diff
|
||||||
|
in `<pre>DIFF</pre>` tags or in the `\[[!format diff """DIFF"""]]` directive.
|
||||||
|
|
||||||
|
Letting user edit `change.tmpl` template to enable this feature is also
|
||||||
|
possible, but this would prevent him from benefiting of the later improvement
|
||||||
|
of this template. In my opinion, an ideal solution would require the user
|
||||||
|
nothing more than enabling some plugins or options.
|
||||||
|
|
||||||
|
-- Louis
|
|
@ -0,0 +1 @@
|
||||||
|
allow option for requiring description when editing page. This is so if a commit to an rcs is used, the commit message will not be blank.
|
Loading…
Reference in New Issue