| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
I had assumed that an image shown full size did not need add_depends, since
a change would not need a change to the displaying page.
But this is not true if the image is modified and its size changes. Then
the page needs to update its img tag to reflect the current size.
|
|
If an image was resized smaller, with width and height specified to values
that did not fit its aspect ratio, the image tag with/height were not
adjusted to the actual size imagemagick chooses.
This was broken by 03449610d6c666ba24bea68f01d896613e522278.
To fix it right, it unfortunatly needs to always read the src image now,
in order to determine if the image is being displayed larger, or resized
smaller. When resized smaller, it then always uses the size of the
thumbnail, while for larger it calculates the size.
(Only way to get rid of this sometimes extra image read would be to change
it to not allow displaying images larger.)
|
|
toplevel index differently etc.
|
|
Through a complex chain of circumstances, that filtering was causing
dumpsetup to trigger undefined warning messages from the po plugin. But
anyway, munging the otl in htmlize is less error-prone and less expensive,
a win all around.
|
|
Allow tempfile to open the file, so it doesn't warn about possible
insecurity. This probably fixes a real, but unlikely security hole too.
|
|
Note that a typical use of this plugin is for a static site, w/o cgi
support enabled.
|
|
Instead, use the change and delete hooks, and launch rsync if either hook
is called.
|
|
|
|
|
|
Conflicts:
IkiWiki/Plugin/rsync.pm
|
|
Avoids needing to specify the path in the rsync command, can just use "."
|
|
yeah, you need branches :P
|
|
|
|
|
|
the last merge. I should really put each feature on its own git branch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Loading and use of IkiWiki::Receive can all be pushed into the git plugin,
rather than scattered around.
I had at first wanted to make a receive plugin and move it there,
but a plugin was not a good fit; you don't want users to have to manually
load it, and making the git plugin load the receive plugin at the right
times would need more, and ugly code.
|
|
|
|
|
|
|
|
|
|
|
|
calls are warranted. They shouldn't modify the caller's working directory,
though. Use File::chdir to keep the scope of the changes subroutine-local.
The tests now pass without resetting the working directory.
|
|
* In Wrapper.pm, add a new hook "wrapperargcheck" to examine argc/argv
and return success or failure. In the failure case, the wrapper
terminates.
* In cvs.pm, implement the new hook to return failure if a directory is
being cvs added.
|
|
|
|
template files in.
|
|
Conflicts:
IkiWiki/Plugin/cvs.pm
|
|
restored just so.
|
|
having to quote, and the possible use of the shell) sucks. Stop
passing args to cvs_runcvs() as an arrayref, since that also sucks
(and was a sop to IPC::Cmd). Instead, use Joey's construction for
temporarily redirecting stderr to /dev/null. Much much simpler and
better. Works on my laptop with bozohttpd, now to test on the NetBSD
wiki.
|
|
|
|
|
|
|
|
|
|
requote in such cases, do quote in all others.
|
|
This reverts commit cdc3576c8d1efb2593cac2d9da3f2393a2afe26e.
Conflicts:
IkiWiki/Plugin/po.pm
This change broke the test suite and is not strictly necessary.
|
|
basewiki. Makes the filetype-testing logic more explicit anyway.
|
|
|
|
|
|
into memory (!)."
|
|
binary file, cvs add -kb it (for attachment support)."
|
|
ikiwiki). Crunch on-demand module loads into one-liners. Comment why
cvsps output is getting read in its entirety and reversed.
|
|
TeX has configuration options that prevent unsafe things like shell
escapes and insecure file reads/writes. Turn all of them on.
teximg's regex-based blacklist does not suffice. For instance:
[[!teximg code="""
\catcode`\%=0
%input{/etc/passwd}
"""]]
Remove the blacklist, since the TeX configuration options seal off the
underlying mechanisms more safely, and the blacklist blocks other TeX
commands that can prove useful.
|
