From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: Add-on: Github Flavored Markdown exporter Date: Wed, 09 Apr 2014 09:03:08 +0200 Message-ID: <87ha63htn7.fsf@gmail.com> References: <87a9bwbx6t.fsf@gmail.com> <878urg12im.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXmWH-0002Fz-8G for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:02:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXmWA-0003yP-7p for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:02:01 -0400 Received: from plane.gmane.org ([80.91.229.3]:56985) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXmWA-0003yG-1E for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 03:01:54 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WXmW9-0008V6-6F for emacs-orgmode@gnu.org; Wed, 09 Apr 2014 09:01:53 +0200 Received: from g231106174.adsl.alicedsl.de ([92.231.106.174]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Apr 2014 09:01:53 +0200 Received: from tjolitz by g231106174.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Apr 2014 09:01:53 +0200 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: emacs-orgmode@gnu.org Lars Tveito writes: > Hi, thanks for checking it out! > Getting it to work with source-blocks was the feature I missed the most > from the vanilla markdown exporter. If you specify a language in the > source-block it will be added to the exported version as well; a problem > occurs if you specify a language not supported by Github. Emacs lisp is > an example of this, so there is a alist `org-gfm-lang' which by default > has the value: > > (("emacs-lisp" . "lisp") ("elisp" . "lisp")) > > So a source block like this: > > #+begin_src emacs-lisp > (defun foo () > 'foo) > #+end_src > > exports to this: > > ```lisp > (defun foo () > 'foo) > ``` > > Which provides syntax highlighting in Github Flavored Markdown. I see, its a feature not a bug ;) To me it looked as if the exporter had failed on this, but as an Org user I never digged very deep in (Github Flavored) Markdown syntax. >> - Just like the Org exporter in general, it does not know how to deal >> with boxes made with rebox2.el, so I replaced them with example >> blocks. >> > > I am not familiar with rebox2.el. This back-end inherits most > functionality from the markdown (vanilla) exporter, which again inherits > from the html exporter. Since rebox2.el doesn't play nice with any of > those it will cause problems with the github flavored as well. > > If you'd like the boxes created with rebox2.el to appear in the exported > version you could possibly wrap it inside an example-block. I think this was basically fixed by Nicolas yesterday, at least when I tried with 'ascii backend the results were quite nice. >> - What about numbered lists with longer text/blocks as item content - is >> the item numbering supposed to work? > > I hadn't tested this, but found an old org-file with notes packed with > different lists. I generated it, and most of it looks good: > https://gist.github.com/anonymous/694b7b5f53dd21850bcd (by the way, the > content is rubbish, and in Norwegian). > > The only problems are with latex-code mixed in the document and sloppy > work from the original org file. I will do some further experiments with this, at first I thought it does not work, but maybe its just me not complying with Org syntax demands (and this would most likely not a specific problem of you exporter neither). -- cheers, Thorsten