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 pretty good results using Stack Overflow's Pagedown library. Here is
the repository (with instructions):
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
On Wed, Jan 18, 2012 at 1:57 PM, Williams, Brian
bwilli...@informatica.com wrote:
Typically, one creates the correctly named page and abandons the original…
On Jan 18, 2012 5:15 AM, Matt Young youngsan...@gmail.com wrote:
I Added a wiki page, I accept the changes then discover you want to
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
Hi everyone,
First, thanks to everyone that has worked on Fossil. It is very, very
useful to me.
I'd like to keep a PDF as embedded documentation (this is a LaTeX
project). Is it possible to do so without bloating the repository too
much?
Thanks,
Guilherme
--
Guilherme P. de Freitas
I have been doing exactly the same thing. A LaTeX (lyx) document plus a
make file that writes out html and a pdf and it seems to work great. I
suppose it may depend on just how much in the way of hard to compress
pictures comprise your document.
I do wish there was a way with the embedded
Hi Matt,
Would you mind sharing that make file? I'm starting a project with Lyx
myself, and that solution seems pretty great!
I thought the embedded docs do preserve the fossil header (such as the
landing page of fossil-scm.org, which is an 'embedded' doc, at least how I
understood the term.)
Hi everyone,
Thanks for your answers, but the question is: won't that bloat the
repository too much?
--
Guilherme P. de Freitas
http://www.gpfreitas.com
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Hey, fossil rename, i'll look for it. Thanks. Right now I am on github, but
still writing embedded sqlite
On Fri, Jan 20, 2012 at 10:12 AM, Ron Wilson ronw.m...@gmail.com wrote:
On Wed, Jan 18, 2012 at 1:57 PM, Williams, Brian
bwilli...@informatica.com wrote:
Typically, one creates the
Sorry, I think the answer to that is it depends. For example do you care
about having a small repository? Are you worried about corruption? For me,
I wouldn't think twice about it. Even a thousand commits, each with their
own pdf of even 1MB is still only 1GB. Unless these are big PDF's, I
This is super!
There is a typo in the install script (referring to hard-coded repo file in
/tmp/...)
- Original Message -
From: Bill Burdick
Sent: 01/21/12 05:24 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] JavaScript Markdown implementation for Fossil
On Fri, Jan
My guess is that you will be better off generating a non-compressed PDF to
reduce repository bloat, if you think that you will be changing it a lot,
because Fossil can do better diff compression that way. The downside would
be that the PDFs will be bigger (of course).
Bill
On Sat, Jan 21,
12 matches
Mail list logo
