On Mon, Aug 18, 2014 at 4:46 PM, Gour wrote:
> On Sun, 17 Aug 2014 13:49:01 -0400
> Ron W wrote:
>
> > And it could be even easier than it is, now, per my suggested
> > enhancement to Fossil.
>
> Where can one read about it?
In my message in this thread on Thu, 14 Aug 2014 18:47:54 -0400
_
On Sun, 17 Aug 2014 13:49:01 -0400
Ron W wrote:
> And it could be even easier than it is, now, per my suggested
> enhancement to Fossil.
Where can one read about it?
Sincerely,
Gour
--
In this endeavor there is no loss or diminution,
and a little advancement on this path can protect
one fr
On Fri, Aug 15, 2014 at 12:55 AM, Gour wrote:
> My intention was not to suggest using AsciiDoc as 'alternative' to the
> Fossil's
>
Nor mine.
> wiki (I had enough in the past when asking for markdown support), but only
> if
> there is some simple way to make it render AsciiDoc documents (for t
On Thu, 14 Aug 2014 14:29:55 -0700
Ross Berteig 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 able to *render*
On Thu, 14 Aug 2014 18:47:54 -0400
Ron W 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 uses [ and ] for
On Thu, Aug 14, 2014 at 3:27 AM, Gour 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 number of feature
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, spec
On Thu, Aug 14, 2014 at 3:39 AM, Stephan Beal wrote:
> On Thu, Aug 14, 2014 at 12:24 PM, Gour 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
On Thu, 14 Aug 2014 12:50:21 +0200
"j. van den hoff"
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 even amidst the threefo
On Thu, 14 Aug 2014 12:39:06 +0200
Stephan Beal 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
vision a learned and
On Thu, Aug 14, 2014 at 1:31 PM, Martin Gagnon wrote:
> If it is possible for google-code-prettify for syntax highlighting, I
> guess it could be for Asciidoctor.js. It's only my 2 cents since I don't
> know much about Asciidoctor.js.
>
That's what the GoCo ones do, and the GoCo parser uses its
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
> envir
On Thu, 14 Aug 2014 12:24:24 +0200, Gour wrote:
On Thu, 14 Aug 2014 10:32:20 +0200
Stephan Beal 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/asci
On Thu, Aug 14, 2014 at 12:39 PM, Stephan Beal
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:
http://fossil-scm.org/index.html/timeline?ym=2008-02&n=35&y=a&u=stephan
They came so
On Thu, Aug 14, 2014 at 12:24 PM, Gour 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 my first contr
On Thu, 14 Aug 2014 10:32:20 +0200
Stephan Beal 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 says:
"https://github.c
On Thu, Aug 14, 2014 at 10:14 AM, Gour 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 custom
front-e
On Thu, 14 Aug 2014 09:56:32 +0200
Stephan Beal 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 Fossil
'speak' AsciiDoc
On Thu, Aug 14, 2014 at 9:27 AM, Gour wrote:
> Now the interesting part in regard to is is Asciidoctor.js - "a
> fully-functional version of Asciidoctor that works in any JavaScript
> environment, such as a web browser or Node.js.", so I wonder whether there
> is
> some possibility to make it in
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 n
20 matches
Mail list logo
