> Sorry I sounded dismissive. You are doing an awesome job, it's
amazing how much it did get right.
No problem at all :)
> My problem is that I am trying to share my sources as code, not as
> documentation. I would like my .org files to be treated as you would
> treat Python code, shown as they
Sebastien,
> For me, an annoying problem is that the Org #+TITLE is treated as
> a simple text, and not outputted as an headline.
> So, if we want an headline on GitHub, we need to create a unique level-1
> heading, which will be shown as the most important section, hence the
> "title". Then, unde
Hello Waldemar,
Waldemar Quevedo wrote:
>> It is rather annoying that github understands the org syntax but not
>> quite, so the sources appear almost but not quite right.
>
> I maintain the parser that is being by Github =>
> https://github.com/wallyqs/org-ruby
> If you let me now the issues I ca
On Mon, Feb 24, 2014 at 8:39 AM, Waldemar Quevedo
wrote:
>> It is rather annoying that github understands the org syntax but not
>> quite, so the sources appear almost but not quite right.
> I maintain the parser that is being by Github =>
> https://github.com/wallyqs/org-ruby
> If you let me now
Hi,
> It is rather annoying that github understands the org syntax but not
quite, so the sources appear almost but not quite right.
I maintain the parser that is being by Github =>
https://github.com/wallyqs/org-ruby
If you let me now the issues I can try to fix them, (or PRs are also
welcome)
Greetings,
I've solved a couple of bugs in the Leanpub[1] markdown exporter[2]
(cross-links within the book using ids were not working, and footnotes
containing a colon neither). As far as I can tell using Orgmode and
Leanpub to publish books is now quite feasible, and produces rather
nice result
