urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

web commit by JeremyReed: reply to two replies

master
joey 2006-12-23 08:04:07 +00:00
parent f4e3e47e12
commit ba53b64fb0
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/index/discussion.mdwn
View File

@ -172,6 +172,12 @@ Any plugins or support for exporting to LaTeX?
> working the way you're thinking of. Noone is currently working on it. > working the way you're thinking of. Noone is currently working on it.
> --[[Joey]] > --[[Joey]]
>> I did some tests with using Markdown and a customized HTML::Latex and html2latex
>> and it appears it will work for me now. (I hope to use ikiwiki for many
>> to collaborate on a printed book that will be generated at least once per day in PDF format.)
>>
>> --JeremyReed
---- ----
# Using with RCS? # Using with RCS?
@ -185,6 +191,15 @@ Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
> that supports web commits with ci, and history (parsing the rcs files by > that supports web commits with ci, and history (parsing the rcs files by
> hand?). If you're a masochist. :-) --[[Joey]] > hand?). If you're a masochist. :-) --[[Joey]]
>> It does have history using rlog(1) which is similar format to "cvs log".
>> I don't think it has any possible hooks. What would happen if I call
>> ikiwiki directly from rcs_commit? (I didn't try yet.) On that note,
>> I don't see any way for ikiwiki to generate a single file, but I guess
>> that doesn't matter as --refresh should be fast enough.
>> I made a Rcs/rcs.pm plugin from Stub. I have been testing it some.
>>
>> --JeremyReed
---- ----
# Using with CVS? # Using with CVS?