emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: aditya siram <aditya.siram@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] Exporting tangled file path
Date: Fri, 18 Oct 2013 11:54:01 -0500	[thread overview]
Message-ID: <CAJrReygw1FvD-=xc24KWNentgwQyr3GH=to01PE=P1wa5tOrhA@mail.gmail.com> (raw)
In-Reply-To: <87a9i61qc0.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Thanks, but I was hoping there was some way of including that in the
exported HTML/PDF etc. That way someone looking at the documentation can
find their way back to the source file. As it stands (at least with the
HTML exporter) there's no way to know where a chunk of code ends up.
-deech


On Fri, Oct 18, 2013 at 11:44 AM, Eric Schulte <schulte.eric@gmail.com>wrote:

> aditya siram <aditya.siram@gmail.com> writes:
>
> > Hi all,
> > Currently when I export a literate program I can see the chunks but not
> > where they end up. It would be really useful if the chunks had a footnote
> > or something that linked to the file where they were tangled. Is there a
> > header argument that does that?
> >
> > Thanks!
> > -deech
>
> Try "C-c C-v" which runs the command org-babel-view-src-block-info on a
> code block.  It will show you if the code block has a specified tangle
> name.  If the value of tangle is "yes" then the name of the Org-mode
> file will be used.
>
> Best,
>
> --
> Eric Schulte
> https://cs.unm.edu/~eschulte
> PGP: 0x614CA05D
>

[-- Attachment #2: Type: text/html, Size: 1701 bytes --]

  reply	other threads:[~2013-10-18 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 14:47 [Babel] Exporting tangled file path aditya siram
2013-10-18 16:44 ` Eric Schulte
2013-10-18 16:54   ` aditya siram [this message]
2013-10-18 17:44     ` Eric Schulte
2013-10-18 17:00 ` Marcin Borkowski

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='CAJrReygw1FvD-=xc24KWNentgwQyr3GH=to01PE=P1wa5tOrhA@mail.gmail.com' \
    --to=aditya.siram@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.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).