From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: ob-lilypond Date: Tue, 28 Jun 2011 22:00:02 +0200 Message-ID: <4E0A32C2.7080908@christianmoe.com> References: <4E09C50D.5020302@christianmoe.com> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:49527) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbeQD-0004Cz-1n for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 15:58:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbeQC-0001Ho-45 for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 15:58:09 -0400 Received: from mars.hitrost.net ([91.185.211.18]:35007) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbeQB-0001Hk-UT for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 15:58:08 -0400 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: Martyn Jago Cc: emacs-orgmode@gnu.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... Yours, Christian