On Thu, 2 Oct 2014 16:07:56 +0200
Stephan Beal sgb...@googlemail.com wrote:
That was unfortunately a bit optimistic of me (i tend towards
pessimism in most estimates ;), for which i apologize. Wiki topics in
general are way, way, way down on my list of eventual todos.
OK, no problem. I,
On Fri, Oct 3, 2014 at 4:56 PM, Gour g...@atmarama.net wrote:
That was unfortunately a bit optimistic of me (i tend towards
pessimism in most estimates ;), for which i apologize. Wiki topics in
general are way, way, way down on my list of eventual todos.
OK, no problem. I, somehow,
On Fri, Oct 3, 2014 at 11:18 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Oct 3, 2014 at 4:56 PM, Gour g...@atmarama.net wrote:
OK, no problem. I, somehow, thought that teaching Fossil to just render
using JS in the browser should not be so hard...
It can do so already, but...
Note that wiki links are generated in many places, most notably the
timeline, and if those links also have to work or the solution is only a
partial one.
(sent from a mobile device - please excuse brevity, typos, and top-posting)
- stephan beal
http://wanderinghorse.net
On Oct 3, 2014 6:02
On Fri, Oct 3, 2014 at 2:01 PM, Stephan Beal sgb...@googlemail.com wrote:
Note that wiki links are generated in many places, most notably the
timeline, and if those links also have to work or the solution is only a
partial one.
I think an example of what I mean would be helpful.
If I go to
On Sun, 28 Sep 2014 16:48:55 -0400
Trevor tre...@breksta.com wrote:
Markdown is versatile, simple format but the multiplicity of
standards limits its universality. I hope you can contribute
to the making of such a standard.
I read a bit about the endeavour to make standard version of
i hear you ;), but as i said at the start of this thread, i am ambivalent
about which format(s) fossil supports, which may be interpreted as i don't
care, as long as someone else implements it ;).
That said... If you have suggestions for a generic api for arbitrary wiki
parsers/filters for
On Thu, 2 Oct 2014 14:43:50 +0200
Stephan Beal sgb...@googlemail.com wrote:
i hear you ;), but as i said at the start of this thread, i am
ambivalent about which format(s) fossil supports, which may be
interpreted as i don't care, as long as someone else implements
it ;).
Well, I am thinking
That was unfortunately a bit optimistic of me (i tend towards pessimism in
most estimates ;), for which i apologize. Wiki topics in general are way,
way, way down on my list of eventual todos.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Oct 2,
On Thu, Oct 2, 2014 at 8:56 AM, Gour g...@atmarama.net wrote:
On Thu, 2 Oct 2014 14:43:50 +0200
Stephan Beal sgb...@googlemail.com wrote:
That said... If you have suggestions for a generic api for arbitrary
wiki parsers/filters for libfossil, i am all ears. :)
As I wrote above, no
On Thu, Oct 2, 2014 at 4:53 PM, Ron W ronw.m...@gmail.com wrote:
As for supporting in-browser wiki rendering, how about adding an option on
the New Wiki Page and Edit Wiki Page pages to choose in-browser
rendering? Then wrap the raw wiki mark-up with div class=wiki.raw
and /div when
On Thu, Oct 2, 2014 at 11:03 AM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Oct 2, 2014 at 4:53 PM, Ron W ronw.m...@gmail.com wrote:
As for supporting in-browser wiki rendering, how about adding an option
on the New Wiki Page and Edit Wiki Page pages to choose in-browser
rendering?
On Sun, Sep 28, 2014 at 11:36 AM, Natacha Porté nata...@instinctive.eu
wrote:
as you might already know, I'm the primary author of libsoldout and its
integration into fossil to perform markdown-to-html conversion.
If you followed recent news, you might have heard of CommonMark[1],
...
A PS to my previous post:
Maybe could call the mark up implemented by libsoldout SoldOut, a safe
subset of MarkDown / CommonMark.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Hello,
as you might already know, I'm the primary author of libsoldout and its
integration into fossil to perform markdown-to-html conversion.
If you followed recent news, you might have heard of CommonMark[1],
which is an attempt to unify most implementations and extensions of
Markdown, by
On Sun, Sep 28, 2014 at 5:36 PM, Natacha Porté nata...@instinctive.eu
wrote:
authors hope). Fortunately, there is no rush to take such a decision, as
a community we can reasonably to wait and see how CommonMark adoption
pans out.
[1]: http://commonmark.org/
i am completely ambivalent on
Hello,
on Sunday 28 September 2014 at 17:58, Stephan Beal wrote:
- Wiki syntaxes have always been a matter of personal taste, and there are
no less than 100 different ones out there in use. To anyone who believes
they can convince people to switch to a common dialect... i've got a
bridge in
On Sun, Sep 28, 2014 at 6:39 PM, Natacha Porté nata...@instinctive.eu
wrote:
I completely share the opinion above, except I'm afraid you have
misunderstood the goal of CommonMark: it's not about unifying or
standardizing wiki format, only unifying Markdown.
i understand that, but there are
http://xkcd.com/927/
--
D. Richard Hipp
Sent from phone - Excuse brevity
On Sep 28, 2014 12:46 PM, Stephan Beal sgb...@googlemail.com wrote:
On Sun, Sep 28, 2014 at 6:39 PM, Natacha Porté nata...@instinctive.eu
wrote:
I completely share the opinion above, except I'm afraid you have
Hello:
Thanks Natasha, for reviewing the CommonMark specification and
identifying issues applicable to your Fossil - Markdown parser.
Your arguments are persuasive.
Your obvious skill and knowledge about markdown and general text
parsing would be of high value to the CommonMark group and I
think
Stephan Beal decía, en el mensaje Re: [fossil-users] Pessimism about
CommonMark in fossil del domingo, 28 de septiembre de 2014 13:45:58:
On Sun, Sep 28, 2014 at 6:39 PM, Natacha Porté nata...@instinctive.eu
mailto:nata...@instinctive.eu wrote:
But this is still about disambiguating
21 matches
Mail list logo
