From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Writing a custom export.
Date: Fri, 13 Aug 2010 12:24:38 -0700 [thread overview]
Message-ID: <877hju48p5.fsf@pellet.net> (raw)
In-Reply-To: AANLkTikvkpX4dMLu-1+xLQ1d8gf-K5KgrjPOCyLVDZff@mail.gmail.com
On Fri, Aug 13 2010, Puneeth wrote:
> Hi Alex,
>
> On Fri, Aug 13, 2010 at 11:39 PM, Alex <elcron@gmail.com> wrote:
>> I've been using emacs + org-mode for ~6 months and haven't done any elisp
>> hacking beyond a custom .emacs file. I would like to write a custom org-mode
>> export to markdown to play around with elisp and so that I can write readmes
>> for my github projects in org-mode. Are there any good tutorials on writing
>> a custom export?
>
> A couple of things,
> 1. Github understands org files. README can be written in org mode also.
> 2. You should look at org-export-generic
> [http://orgmode.org/worg/org-contrib/org-export-generic.php] in case
> you wish to continue with writing your custom export to markdown.
>
Hey, this is great! I didn't know this existed. But to be useful for
Markdown (which I'd also like very much), it would need options for
formatting emph and strong regexs (currently '/' and '*' in org-mode,
would need to be '*' and '**' for Markdown) and also links.
I'm not sure what :body-tags-{prefix,suffix} actually do, but that
sounds promising. Link formatting would need to be added, but it seems
like adding a :body-link-address and :body-link-description would pretty
much take care of it.
If this isn't currently doable without patching org-export-generic.el, I
can take a stab at providing such a patch (unless Alex was hankering for
a weekend project :)).
Eric
>> Thanks, Alex Henning
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>>
prev parent reply other threads:[~2010-08-13 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 18:09 Writing a custom export Alex
2010-08-13 18:36 ` Puneeth
2010-08-13 19:24 ` Eric Abrahamsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hju48p5.fsf@pellet.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).