From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waldemar Quevedo Subject: Re: Writing your book with orgmode and publishing it on Leanpub Date: Mon, 24 Feb 2014 21:26:55 +0900 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d0447f0ee8774c704f32617e1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHucw-0006UT-Mm for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:27:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHucu-0005LO-RZ for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:27:18 -0500 Received: from mail-ob0-x233.google.com ([2607:f8b0:4003:c01::233]:55229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHucu-0005L6-Kk for emacs-orgmode@gnu.org; Mon, 24 Feb 2014 07:27:16 -0500 Received: by mail-ob0-f179.google.com with SMTP id wn1so1894597obc.24 for ; Mon, 24 Feb 2014 04:27:16 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Juan Reyero Cc: org-mode Mailing List --f46d0447f0ee8774c704f32617e1 Content-Type: text/plain; charset=ISO-8859-1 > 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 are and syntax-highlighted. I've been trying to have syntax highlighting available for documents rendered in Github for a while now. Possibly when this pull request is accepted thinks would be highlighted: https://github.com/github/markup/pull/254 > That said, the one place where the translation fails is when the > source code of babel snippets should not be exported. Again, probably > due to the tension between the need to show the file's content and the > desire to render it as a document. I think this might be because :exports none|both|source is currently not implemented for source code blocks, I will try to get this included in the next version of the gem. Thanks for the feedback, and please if you find another issue let me know by creating an issue :) Regards, - Wally On Mon, Feb 24, 2014 at 5:33 PM, Juan Reyero wrote: > 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 the issues I can try to fix them, (or PRs are also > > welcome).... > > Sorry I sounded dismissive. You are doing an awesome job, it's > amazing how much it did get right. > > 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 are and syntax-highlighted. If you > parse them you will inevitably miss the context I am relying upon to > render them properly (like when you ---rightly--- assume that html > should be left standing, but what I wrote expects a jekyll > post-process). > > People visiting the repository will most likely be interested in what > I actually wrote, not in its rendering as a document. Close to what > you get when you select Raw, but syntax-highlighted. This is what I > want the repository for; the document is somewhere else. > > That said, the one place where the translation fails is when the > source code of babel snippets should not be exported. Again, probably > due to the tension between the need to show the file's content and the > desire to render it as a document. > > > I have this example > > where you can use `#+layout:` instead of YAML. > > https://github.com/wallyqs/yet-another-jekyll-org-template > > https://github.com/eggcaker/jekyll-org/blob/master/convert.rb#L30 > > Thank you for the pointer. > > Best, > > jm > > > On Mon, Feb 24, 2014 at 4:24 AM, Juan Reyero wrote: > >> > >> 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 results. > >> > >> I have also published the sources for my book, The Hacker Ways[3], at > >> > >> https://github.com/juanre/hacker-ways > >> > >> It is rather annoying that github understands the org syntax but not > >> quite, so the sources appear almost but not quite right. Clone and > >> open in Emacs to see what's going on. > >> > >> Best regards, > >> > >> jm > >> -- > >> http://greaterskies.com > >> http://juanreyero.com > >> > >> [1] Leanpub.com is a very nice self-publishing platform. I am not > >> associated with them, and they are not responsible for my code. > >> > >> [2] http://juanreyero.com/open/ox-leanpub/ > >> > >> [3] https://leanpub.com/hackerways/ > >> > > > > > > -- > http://greaterskies.com > http://juanreyero.com > --f46d0447f0ee8774c704f32617e1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
> Sorry I sounded dismissive. =A0You 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 m= y sources as code, not as
> documentation. =A0I would like my .org files to be treated as you wou= ld
> treat Python code, shown as they are and syntax-highlighted.=A0
I've been trying to have syntax highlighting availab= le for documents rendered in Github
for a while now. = Possibly when this pull request is accepted thinks would be highlighted:
https://github.com/github/markup/pull/254

> That = said, the one place where the translation fails is when the
> source code of babel snippets should not be exported. =A0Again, proba= bly
> due to the tension between the need to show the file's content an= d the
> desire to render it as a document.
I think this mi= ght be because :exports none|both|source is currently not implemented
for source code blocks, I will try to= get this included in the next version of the gem.

Thanks for the feedback, and please if you find another issue let me = know by creating an issue :)

Regards,=A0

- Wally<= /div>



On Mon, Feb 24, 2014 at 5:33 PM, Juan Reyero <joanmg@gmail.com> wrote:
On Mon, Feb 24, 2014 at 8:39= AM, Waldemar Quevedo
<waldemar.quevedo@gmail.co= m> wrote:
>> It is rather annoying that github understands the org syntax but n= ot
>> quite, so the sources appear almost but not quite right.
> I maintain the parser that is being by Github =3D>
> http= s://github.com/wallyqs/org-ruby
> If you let me now the issues I can try to fix them, (or PRs are also > welcome)....

Sorry I sounded dismissive. =A0You are doing an awesome job, it's=
amazing how much it did get right.

My problem is that I am trying to share my sources as code, not as
documentation. =A0I would like my .org files to be treated as you would
treat Python code, shown as they are and syntax-highlighted. =A0If you
parse them you will inevitably miss the context I am relying upon to
render them properly (like when you ---rightly--- assume that html
should be left standing, but what I wrote expects a jekyll
post-process).

People visiting the repository will most likely be interested in what
I actually wrote, not in its rendering as a document. =A0Close to what
you get when you select Raw, but syntax-highlighted. =A0This is what I
want the repository for; the document is somewhere else.

That said, the one place where the translation fails is when the
source code of babel snippets should not be exported. =A0Again, probably due to the tension between the need to show the file's content and the<= br> desire to render it as a document.

> I have this example
> where you can use `#+layout:` instead of YAML.
> https://github.com/wallyqs/yet-another-jekyll-org-templa= te
> https://github.com/eggcaker/jekyll-org/blob/maste= r/convert.rb#L30

Thank you for the pointer.

Best,

jm

> On Mon, Feb 24, 2014 at 4:24 AM, Juan Reyero <joanmg@gmail.com> wrote:
>>
>> Greetings,
>>
>> I've solved a couple of bugs in the Leanpub[1] markdown export= er[2]
>> (cross-links within the book using ids were not working, and footn= otes
>> containing a colon neither). =A0As far as I can tell using Orgmode= and
>> Leanpub to publish books is now quite feasible, and produces rathe= r
>> nice results.
>>
>> I have also published the sources for my book, The Hacker Ways[3],= at
>>
>> https://github.com/juanre/hacker-ways
>>
>> It is rather annoying that github understands the org syntax but n= ot
>> quite, so the sources appear almost but not quite right. =A0Clone = and
>> open in Emacs to see what's going on.
>>
>> Best regards,
>>
>> jm
>> --
>> http://great= erskies.com
>> http://juanrey= ero.com
>>
>> [1] Leanpub.com is a very nice self-publishing platform. =A0I am n= ot
>> associated with them, and they are not responsible for my code. >>
>> [2] http://juanreyero.com/open/ox-leanpub/
>>
>> [3] = https://leanpub.com/hackerways/
>>
>



--
http://greaterskies.c= om
http://juanreyero.com

--f46d0447f0ee8774c704f32617e1--