On May 11, 2018, at 7:21 PM, Will Parsons wrote:
>
> How could I come across this solution on my own?
Most of what it does is described here, which is well worth a read if you
haven’t done so already:
https://fossil-scm.org/index.html/doc/trunk/www/embeddeddoc.wiki
On Friday, 11 May 2018 10:43 AM -0400, Warren Young wrote:
> On May 11, 2018, at 8:09 AM, Richard Hipp wrote:
>>
>> License
>
> If that works, then I’d strongly suggest text/plain instead. You don’t want
> Fossil to tell the browser that it should try interpreting
On May 10, 2018, at 4:50 PM, Will Parsons wrote:
>
> I know (at least I think I know) that I can get the effect I want by
> making the file a Markdown file by renaming it LICENCE.md
Yes. Scroll to the final paragraph of this Fossil wiki document for a case in
point:
On May 11, 2018, at 8:09 AM, Richard Hipp wrote:
>
> License
If that works, then I’d strongly suggest text/plain instead. You don’t want
Fossil to tell the browser that it should try interpreting ampersands and angle
brackets in the plain text of the license.
On 5/10/18, Will Parsons wrote:
> I've just added a plain-text LICENCE file to one of my projects that uses
> Fossil, and I'd like to add a link to it from the project homepage that will
> display the file's contents when the link is followed. I thought the
> obvious
>
5 matches
Mail list logo