emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-lilypond
Date: Tue, 28 Jun 2011 22:00:02 +0200	[thread overview]
Message-ID: <4E0A32C2.7080908@christianmoe.com> (raw)
In-Reply-To: <loom.20110628T190134-157@post.gmane.org>

> This is very doable since it is the first thing I tried on initial
> experimentation. I think I had some difficulty cropping the snippet (png)
> in that the result had no padding at all, but I'm guessing that can be
> overcome.

I guess most of us who would be interested in this would have 
ImageMagick *convert* at hand, if it's difficult to get Lilypond or 
lilypond-book to do it directly.

> Certainly with the use cases you suggest, the defaults would need to
> change, and C-c C-c would need to act as you describe, but that wouldn't
> be an issue if we can define seperate 'modes' for the different ways of
> working (I think for now the 'modes' can be considered  mutually exclusive).

I'd tentatively suggest things should be done in a way that is roughly 
analogous with how other Babel languages work, not in the way that 
makes one or another use case super-easy to do. For our different use 
cases we might then each have to tweak some :tangle, :exports, 
:results or :file header arguments.

But using Org-Babel's provisions for system-wide, language-specific 
and buffer-wide heading arguments, the user should be able to define 
her own `modes' by changing a few settings, and avoid littering a 
complex document with those header arguments.

Maybe. Haven't thought this very far through...


  parent reply	other threads:[~2011-06-28 19:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 13:00 ob-lilypond Martyn Jago
2011-06-27 18:53 ` ob-lilypond Eric Schulte
2011-06-28  9:38   ` ob-lilypond Martyn Jago
2011-06-28 10:07     ` ob-lilypond Bastien
2011-06-28 10:21       ` ob-lilypond Bastien
2011-06-28 20:45         ` ob-lilypond Eric Schulte
2011-06-28 23:07           ` ob-lilypond Bastien
2011-06-29  0:41             ` ob-lilypond Eric Schulte
2011-06-29 17:07           ` ob-lilypond Martyn Jago
2011-06-29 21:15             ` ob-lilypond Eric Schulte
2011-06-30  6:38               ` ob-lilypond Martyn Jago
2011-06-30 18:10                 ` ob-lilypond Eric Schulte
2011-07-01 12:01                   ` ob-lilypond Christian Moe
2011-07-06  8:13                     ` [BABEL][PATCH] ob-lilypond basic mode - was ob-lilypond Martyn Jago
2011-07-06 13:20                       ` Eric Schulte
2011-07-01 13:43                   ` ob-lilypond Martyn Jago
2011-07-01 19:27                     ` ob-lilypond Eric Schulte
2011-07-02 13:04                       ` ob-lilypond Martyn Jago
2011-06-28 13:38     ` ob-lilypond Cameron Horsburgh
2011-06-28 16:46       ` ob-lilypond Martyn Jago
2011-06-28 12:11 ` ob-lilypond Christian Moe
2011-06-28 13:18   ` ob-lilypond David O'Toole
2011-06-28 17:06   ` ob-lilypond Martyn Jago
2011-06-28 18:51     ` ob-lilypond Christian Moe
2011-06-28 19:00     ` ob-lilypond Michael Brand
2011-06-28 20:00     ` Christian Moe [this message]
2011-06-28 21:19       ` ob-lilypond Martyn Jago
  -- strict thread matches above, loose matches on Subject: below --
2015-03-25 12:49 ob-lilypond pls
2015-03-26  9:20 ` ob-lilypond pls
2015-03-29 21:27   ` ob-lilypond Nick Dokos
2015-03-30  9:20     ` ob-lilypond Patrick L. Schmidt
2015-03-26  9:26 ob-lilypond Patrick L. Schmidt

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:

  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=4E0A32C2.7080908@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=martyn.jago@btinternet.com \


* 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


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).