From: Eric Schulte <schulte.eric@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Torsten Anders <torsten.anders@beds.ac.uk>, emacs-orgmode@gnu.org
Subject: Re: Thanks for Lilypond export (and minor comments)
Date: Thu, 07 Jul 2011 19:35:31 -0600 [thread overview]
Message-ID: <874o2x1rfz.fsf@gmail.com> (raw)
In-Reply-To: 87sjqhdfn3.fsf@gnu.org
Bastien <bzg@altern.org> writes:
> Hi Torsten,
>
> Torsten Anders <torsten.anders@beds.ac.uk> writes:
>
>> Some brief comments. Support for additional languages like Lilypond and
>> also awk should be celebrated by including them in the list of languages in
>> the documentation (http://orgmode.org/org.html#Languages).
>
> Fixed in latest org.texi -- thanks!
>
>> I first had to load dot support (because you are calling
>> org-babel-expand-body:dot). If you want to also attract musicians (without
>> Org-programming experience themselves) it might be a good idea to very
>> clearly document this dependency (or to remove it).
>
> I let Martyn or Eric put a stab at this.
>
> Thanks,
Thanks for finding this error Torsten! I've just pushed up a fix.
Bastien,
is there a process for bug-fix commits like this one which should be
pushed through to Emacs24? I'm thinking a branch (maintenance?) to
which this should be pushed or a special way to tag the commit?
Thanks -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-07-08 1:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 16:38 Thanks for Lilypond export (and minor comments) Torsten Anders
2011-07-07 20:01 ` Bastien
2011-07-08 1:35 ` Eric Schulte [this message]
2011-07-08 6:13 ` Bastien
2011-07-08 7:00 ` Nick Dokos
2011-07-08 9:08 ` Bastien
2011-07-08 16:02 ` Suvayu Ali
2011-07-09 8:44 ` Bastien
2011-07-10 16:50 ` Suvayu Ali
2011-07-11 16:50 ` Bastien
2011-07-11 17:50 ` suvayu ali
2011-07-19 12:29 ` Bernt Hansen
2011-07-19 12:40 ` suvayu ali
2011-07-08 21:00 ` Achim Gratz
2011-07-09 8:46 ` Bastien
2011-07-08 7:56 ` Martyn Jago
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874o2x1rfz.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=torsten.anders@beds.ac.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.