On Fri, Jan 20, 2012 at 7:48 PM, Ron Wilson <ronw.m...@gmail.com> wrote:
> On Fri, Jan 20, 2012 at 9:00 AM, Bill Burdick <bill.burd...@gmail.com> > wrote: > > The Markdown discussion got me thinking and, as is my wont, I decided to > try > > adding Markdown to Fossil without changing the executable. I think I got > > > > To make a wiki page use Pagedown (from the fossil wiki or from a "doc" > > page), just put @pagedown at the top. > > Sounds good. I will try this later today. > > Two thoughts: > > 1. Your use of // conflicts with normal URL processing. Even without > the http: or https:, // introduces a host name. That is, a URL of the > form > > //name.domain/path/to/page > > should look for "/path/to/page" on the host "name.domain", not the > path "//name.domain/path/to/page" on the current host. > Thanks, I didn't know that! Now, I need a nice way to specify a "repository-local" URL. I guess I could just use $baseurl. Any other ideas? 2. To avoid Fossil's wiki redering, wouldn't you need: > > <nowiki> > @pagedown > Markdown content > </nowiki> > <nowiki> is not necessary because I don't avoid Fossil's rendering -- my code hides Fossil's wiki rendering, grabs the original wiki source (not the rendered content), generates the Pagedown output for the source, dynamically replaces the rendering that Fossil did with the Pagedown output, and then shows the result. This keeps it simpler for people, so all they have to do is just put @pagedown at the top. Bill
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
