From: Grant Rettke <gcr@wisdomandwonder.com>
To: Thomas Morgan <tlm@ziiuu.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Adding source location information when tangling
Date: Tue, 27 May 2014 11:23:59 -0500 [thread overview]
Message-ID: <CAAjq1md_Odzt2o69_yoQ7nhiqxdoXXE7WUwpiVW+pCw8KvM0gg@mail.gmail.com> (raw)
In-Reply-To: <87zji5bz6s.fsf@azha.ziiuu.com>
Something like "
Jumping between code and Org
here?
http://orgmode.org/manual/Extracting-source-code.html#Extracting-source-code
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Sun, May 25, 2014 at 11:28 AM, Thomas Morgan <tlm@ziiuu.com> wrote:
> Dear Org hackers,
>
> I have a question about tangling LilyPond code blocks.
>
> Is there a way to put the commands `\sourcefilename' and
> `\sourcefileline' in the tangled file before each block,
> perhaps in place of the comment that includes the same information?
> (These commands are equivalent to the `#line LINENUM "FILE"'
> directive in C.) If possible I'd like to let LilyPond know how
> to give error messages that refer to the originating Org file.
>
> Thanks,
> Thomas
>
next prev parent reply other threads:[~2014-05-27 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 16:28 Adding source location information when tangling Thomas Morgan
2014-05-27 16:23 ` Grant Rettke [this message]
2014-05-27 21:08 ` Rainer M Krug
2014-05-28 21:48 ` Thomas Morgan
2014-05-29 13:56 ` Rainer M Krug
2014-06-06 16:24 ` Eric Schulte
2014-06-07 4:23 ` Thomas Morgan
2014-06-07 15:28 ` Eric Schulte
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=CAAjq1md_Odzt2o69_yoQ7nhiqxdoXXE7WUwpiVW+pCw8KvM0gg@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=emacs-orgmode@gnu.org \
--cc=tlm@ziiuu.com \
/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).