Simplify mdwn.pm Markdown::Markdown error message.
Avoids:
../IkiWiki/Plugin/mdwn.pm:100: invalid variable interpolation at "$"
Remove mdwn.pm checkconfig() definition.
1) I'd never registered it.
2) We *don't* want to configure markdown_path by default, because when
its defined it overrides any perl modules (e.g. Text::Markdown).
Make it easy to select a Markdown executible.
For example, if you want to use a local version of Markdown to work
around bugs in your system's version.
The latest version of Gruber's Markdown seems to be:
http://daringfireball.net/projects/downloads/Markdown_1.0.2b8.tbz
Release note:
http://six.pairlist.net/pipermail/markdown-discuss/2007-May/000615.html
Debian experimental is using this 1.0.2b8 version:
http://packages.debian.org/search?keywords=markdown
There are many other implementations as well, and most seem to support
the
/path/to/markdown SOURCE
syntax, printing the marked up XHTML to stdout. This patch makes it
easy to drop in any executable you wish.
Add path and path_natural sort orders
These correspond to title and title_natural, but compare the entire
path: a < a/b < a/z < ab < b.
(cherry picked from commit
903a5a314f1f5d833dbc208ce128f24195b40e4b)
Consume all stdin when rcs_receive short-circuits, to avoid git SIPIPE race.
We had a weird problem where, after moving to a new, faster server,
"git push" would sometimes fail like this:
Unpacking objects: 100% (3/3), done.
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
What turned out to be going on was that git-receive-pack was dying due
to an uncaught SIGPIPE. The SIGPIPE occurred when it tried to write to
the pre-receive hook's stdin. The pre-receive hook, in this case, was
able to do all the checks it needed to do without the input, and so did
exit(0) without consuming it.
Apparently that causes a race. Most of the time, git forks the hook,
writes output to the hook, and then the hook runs, ignores it, and exits.
But sometimes, on our new faster server, git forked the hook, and it
ran, and exited, before git got around to writing to it, resulting in
the SIGPIPE.
write(7, "
c9f98c67d70a1cfeba382ec27d87644a"..., 100) = -1 EPIPE (Broken
pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
I think git should ignore SIGPIPE when writing to hooks. Otherwise,
hooks may have to go out of their way to consume all input, and as I've
seen, the races when they fail to do this can lurk undiscovered.
I have written to the git mailing list about this.
As a workaround, consume all stdin before exiting.
add news item for ikiwiki 3.
20111107
graphviz: Support wikilinks embedded in the graph.
(Sponsored by The TOVA Company.)
graphviz: Support urls embedded in the graph, by having graphviz generate an imagemap.
Also, I let preview mode write real files, rather than using data: uri.
Which is ok these days, since ikiwiki tracks files created during
previewing, and cleans them up later.
The umask setting can now be set to private, group, or public, avoiding the need to enter octal correctly which is particularly difficult in yaml setup files. (smcv)
I have no branch and must merge.
editpage: Fix FormattingHelp link on Discussion pages.
In
875d550f1278215e6c87d3b78ff87db24c6d76b3 I for some reason
made $page be changed when creating a discussion page, which
broke the link on the edit page. Changing page seems unnecessary,
so reverted that part of the change.
when octal and YAML collide...
projects / ikiwiki.git / log