fix bad example of exclude configuration item, and remove some stuff about

it from discussion, since it is indeed documented
master
joey 2006-12-28 23:46:55 +00:00
parent 61be019855
commit 98d71ccef5
2 changed files with 1 additions and 25 deletions

View File

@ -81,7 +81,7 @@ use IkiWiki::Setup::Standard {
discussion => 1, discussion => 1,
# To exclude files matching a regexp from processing. This adds to # To exclude files matching a regexp from processing. This adds to
# the default exclude list. # the default exclude list.
#exclude => qr/\*.wav/, #exclude => qr/*\.wav/,
# Time format (for strftime) # Time format (for strftime)
#timeformat => '%c', #timeformat => '%c',
# Locale to use. Must be a UTF-8 locale. # Locale to use. Must be a UTF-8 locale.

View File

@ -188,30 +188,6 @@ Moved to [[bugs]] -- [[Joey]]
---- ----
# wiki\_file\_regexp and RCS ,v files
I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup.
I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree.
What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree?
-- [[JeremyReed]]
> Add the ,v to the $config{wiki\_file\_prune\_regexps} array. This is how we
> skip equivilant files from other revision control systems too.
> --[[Joey]]]
>> Okay, I used in my setup configuration:
>> exclude => qr/\,v$/,
>> I looked in source for the array you mentioned above and noticed the $setup{exclude}. And now I see that is documented.
>> (By the way, the example there doesn't seem correct with a literal asterisk and period wildcard.
>> Maybe it should be qr/\.wav$/,)
>> --[[JeremyReed]]
----
# Textile Plugin # Textile Plugin
It was trivial, but I put together a plugin that uses the Textile markup It was trivial, but I put together a plugin that uses the Textile markup