Hello,
the topic of the markup in Fossil is quite an old one and in the past there was
a thread about using AsciiDoc markup which can be rendered with
https://github.com/srackham/asciidoc-fossil-backend.
Recently I've became interested (again) into using AsciiDoc feeling that
markdown is simply
On Thu, 14 Aug 2014 09:56:32 +0200
Stephan Beal sgb...@googlemail.com wrote:
You can in fact do that with the JSON API. i've been serving Google
Code-format wiki pages this way for a a couple years now:
Very interersting!
Does it mean there is nothing interesting in Asciidoctor.js to make
On Thu, Aug 14, 2014 at 10:14 AM, Gour g...@atmarama.net wrote:
Does it mean there is nothing interesting in Asciidoctor.js to make Fossil
'speak' AsciiDoc?
Correct, but it also means that if you try to view those pages in the
fossil wiki, they will be mangled. For those 3 sites i use only my
Just an idea:
f g somefile --to trunk
gives this error: “must use --from if --to is present”, while:
f g somefile --from trunk
f g somefile --from current --to trunk (same as before but opposite direction)
both work just fine. So, why not make the “--from current” the default when no
--from
Hi,
If I start the ui by doing `fossil ui` in the directory of an open
checkout, the ui pages don't except prev/next/current as valid revision
names. Is this a bug? I am using fossil on Windows. Is this true also on
Linux, or does it have to do with fossil starting a new instance to serve
HTTP
On Mon, Aug 11, 2014 at 10:40 PM, Tony Papadimitriou to...@acm.org wrote:
f g somefile --from trunk
f g somefile --from current --to trunk (same as before but opposite
direction)
both work just fine. So, why not make the “--from current” the default
when no --from option is found,
On Thu, 14 Aug 2014 10:32:20 +0200
Stephan Beal sgb...@googlemail.com wrote:
Correct, but it also means that if you try to view those pages in the
fossil wiki, they will be mangled.
That's clear, but originally I was thinking about
https://github.com/srackham/asciidoc-fossil-backend which
On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote:
https://github.com/srackham/asciidoc-fossil-backend which says:
https://github.com/srackham/asciidoc-fossil-backend;
Sorry, i missed that part. i'm glad to see someone gets some use out of the
wiki CLI commands (IIRC those were
On Thu, Aug 14, 2014 at 12:39 PM, Stephan Beal sgb...@googlemail.com
wrote:
i'm glad to see someone gets some use out of the wiki CLI commands (IIRC
those were my first contributions to Fossil).
Fossil says otherwise, though:
On Thu, Aug 14, 2014 at 12:03 PM, Baruch Burstein bmburst...@gmail.com
wrote:
If I start the ui by doing `fossil ui` in the directory of an open
checkout, the ui pages don't except prev/next/current as valid revision
names. Is this a bug?
The UI only uses the repo, not the checkout, and the
On Thu, Aug 14, 2014 at 12:47 PM, Stephan Beal sgb...@googlemail.com
wrote:
The UI only uses the repo, not the checkout
That's apparently wrong, or possibly command-dependent. (Forgot to delete
it.)
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom
On Thu, 14 Aug 2014 12:24:24 +0200, Gour g...@atmarama.net wrote:
On Thu, 14 Aug 2014 10:32:20 +0200
Stephan Beal sgb...@googlemail.com wrote:
Correct, but it also means that if you try to view those pages in the
fossil wiki, they will be mangled.
That's clear, but originally I was thinking
On Thu, Aug 14, 2014 at 6:32 AM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Aug 14, 2014 at 12:16 PM, Stephan Beal sgb...@googlemail.com
wrote:
On Mon, Aug 11, 2014 at 10:40 PM, Tony Papadimitriou to...@acm.org
wrote:
f g somefile --from trunk
f g somefile --from current --to
On Thu, Aug 14, 2014 at 1:47 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Aug 14, 2014 at 12:03 PM, Baruch Burstein bmburst...@gmail.com
wrote:
Interestingly... it does work on linux with ui, at least with the /dir
page. This may be page-dependent. Which pages aren't working for
On Thu, Aug 14, 2014 at 09:56:32AM +0200, Stephan Beal wrote:
On Thu, Aug 14, 2014 at 9:27 AM, Gour [1]g...@atmarama.net wrote:
Now the interesting part in regard to is is Asciidoctor.js � - a
fully-functional version of Asciidoctor that works in any JavaScript
environment,
Oh i see, thank you very much.
Alysson Gonçalves de Azevedo
Anarcho-syndicalism is a way of preserving freedom. - Monty Python
2014-08-11 18:08 GMT-03:00 Scott Robison sc...@casaderobison.com:
On Mon, Aug 11, 2014 at 2:36 PM, Alysson Gonçalves de Azevedo
agalys...@gmail.com wrote:
I
On Thu, Aug 14, 2014 at 1:03 PM, Baruch Burstein bmburst...@gmail.com
wrote:
If I start the ui by doing `fossil ui` in the directory of an open
checkout, the ui pages don't except prev/next/current as valid revision
names. Is this a bug? I am using fossil on Windows. Is this true also on
On Thu, 14 Aug 2014 12:39:06 +0200
Stephan Beal sgb...@googlemail.com wrote:
Indeed. It's called LaTeX ;).
I like LaTeX's output and used it for printed books along with LyX, but it's
simply not very readable.
Sincerely,
Gour
--
The humble sages, by virtue of true knowledge, see with equal
On Thu, Aug 14, 2014 at 2:31 PM, Baruch Burstein bmburst...@gmail.com
wrote:
BTW, why is this done like this on Windows, instead of doing the same as
linux (where the HTTP requests are handled directly by the server instance
of fossil)?
Can't say - i don't do Windows. It surprises me as
On Thu, 14 Aug 2014 12:50:21 +0200
j. van den hoff veedeeh...@googlemail.com
wrote:
I thus quite probably still would prefer the LaTeX route for serious
typesetting. but overall asciidoc is really great.
Don't forget there is Pandoc. ;)
Sincerely,
Gour
--
One who is not disturbed in mind
On Thu, Aug 14, 2014 at 3:43 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Aug 14, 2014 at 2:31 PM, Baruch Burstein bmburst...@gmail.com
wrote:
BTW, why is this done like this on Windows, instead of doing the same as
linux (where the HTTP requests are handled directly by the server
On Thu, Aug 14, 2014 at 2:58 PM, Baruch Burstein bmburst...@gmail.com
wrote:
I can't figure out the logic behind this system.
== Win32
There's also boatloads Windows-only stuff in the string conversions (which
are all no-ops on non-Windows, except for a couple which do Mac stuff).
Reason:
On Thu, Aug 14, 2014 at 8:31 AM, Baruch Burstein bmburst...@gmail.com
wrote:
On Thu, Aug 14, 2014 at 1:03 PM, Baruch Burstein bmburst...@gmail.com
wrote:
If I start the ui by doing `fossil ui` in the directory of an open
checkout, the ui pages don't except prev/next/current as valid revision
On Thu, Aug 14, 2014 at 3:39 AM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote:
https://github.com/srackham/asciidoc-fossil-backend which says:
https://github.com/srackham/asciidoc-fossil-backend;
Sorry, i missed that part. i'm
Personally, I don't see much need for fossil to have built-in support
for rendering anything much richer than its own wiki or the vanilla
markdown we have now.
I happily use fossil as-is for storing writing projects. Lately I write
in a combination of markdown and LaTeX (usually LuaLaTeX,
On Thu, Aug 14, 2014 at 3:27 AM, Gour g...@atmarama.net wrote:
the topic of the markup in Fossil is quite an old one and in the past
there was
a thread about using AsciiDoc markup which can be rendered with
I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered
a huge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I attempted to push via Citrix's \\client mechanism, but got this failure:
H:\fossil fossil push -R repository.fossil -once
file:client/c$/users/andy/desktop/work/fossil/repository.fossil
Round-trips: 5 Artifacts sent: 4 received: 0
Error: bad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/14/2014 6:28 PM, Andy Goth wrote:
H:\fossil fossil push -R repository.fossil -once
file:client/c$/users/andy/desktop/work/fossil/repository.fossil
Round-trips: 5 Artifacts sent: 4 received: 0
Error: bad command: j~~lqL\
At this
Thus said Andy Goth on Thu, 14 Aug 2014 18:28:03 -0500:
At this point the only thing I can think to do is shun the large files
I can do without, then reconstruct a much smaller repository.
So is it because of the big files that this is happening? Just how big
are these files?
Andy
--
TAI64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/14/2014 8:56 PM, Andy Bradford wrote:
Thus said Andy Goth on Thu, 14 Aug 2014 18:28:03 -0500:
At this point the only thing I can think to do is shun the large
files I can do without, then reconstruct a much smaller
repository.
So is it
On Thu, 14 Aug 2014 18:47:54 -0400
Ron W ronw.m...@gmail.com wrote:
I looked at AsciiDoc. In theory, it's nice, but it appears to have
gathered a huge number of features over the years. It really appears
to try to be LaTeX Light.
As it was already said, readability counts here.
Also, it
On Thu, 14 Aug 2014 14:29:55 -0700
Ross Berteig r...@cheshireeng.com wrote:
Personally, I don't see much need for fossil to have built-in support
for rendering anything much richer than its own wiki or the vanilla
markdown we have now.
I agree and as I already replied the idea is just to be
32 matches
Mail list logo
