emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Steven Arntson <steven@stevenarntson.com>
To: emacs-orgmode@gnu.org
Subject: Re: more from org-babel newbie
Date: Mon, 28 Apr 2014 19:31:13 -0700	[thread overview]
Message-ID: <877g68amtq.fsf@stevenarntson.com> (raw)
In-Reply-To: m2fvkw6gfw.fsf@tsdye.com

tsd@tsdye.com (Thomas S. Dye) writes:

> Aloha Steven,
> Steven Arntson <steven@stevenarntson.com> writes:
>> The reason I'm excited to use org with lilypond files is the foldable
>> headers *, **, *** etc, as well as drawers and tables. However, that's
>> available only in an "org-mode" buffer, and I'm also wanting to use
>> lilypond-mode, which gives excellent colored markup and indentation. How
>> do I get the advantages of both? Or is that not even what I should be
>> after? I may be fundamentally missing what's potentially useful about
>> all of this for my musical use case!
> I haven't used babel for lilypond, but the usual way to edit a source
> code block in the emacs mode for the language is to press C-c ' in the
> source code block.
> hth,
> Tom

This is embarrassing ... I'd tried that and hadn't managed to get it to
work, and now I realize I was using C-c ` and not C-c '. The devil is in
the details.

I'm still a little mystified about using org markup in the context of
the lilypond file, but maybe now I can do a little more experimenting.

Thank you!

  reply	other threads:[~2014-04-29  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  1:22 more from org-babel newbie Steven Arntson
2014-04-29  2:02 ` Thomas S. Dye
2014-04-29  2:31   ` Steven Arntson [this message]
2014-04-29  2:44     ` Thomas S. Dye

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=877g68amtq.fsf@stevenarntson.com \
    --to=steven@stevenarntson.com \
    --cc=emacs-orgmode@gnu.org \


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