From: "Thomas S. Dye" <tsd@tsdye.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: [babel] editing LaTeX source code blocks
Date: Mon, 23 Nov 2009 11:34:35 -1000 [thread overview]
Message-ID: <475706D8-9D64-4427-A44E-3FAA851FD22F@tsdye.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --]
Aloha all,
It is very convenient in org-babel to open a new buffer on a source
code block with C-c ' and edit in that buffer using the appropriate
Emacs major/minor modes.
Currently, the LaTeX source code buffer doesn't have access to labels
defined in other source code blocks. Outside of org-babel, when
editing multi-file documents, reftex (or auctex, I'm not sure which)
scans all the files referenced in the master file for labels and makes
these available when adding a cross reference.
It would be nice if C-c ' on a LaTeX source code block did something
similar, perhaps by finding LaTeX source code blocks with a :tangle
header argument and evaluating the noweb references to find label
definitions.
If it is the case that the Org-mode file contains more than one LaTeX
source code block with a :tangle header argument, then perhaps the
user could be given a choice of which one to search for label
definitions.
There are easy workarounds for this, so it isn't a big deal. It would
be deluxe to leverage the full power of reftex while editing org-babel
LaTeX source code blocks, though.
All the best,
Tom
Thomas S. Dye, Ph.D.
T. S. Dye & Colleagues, Archaeologists, Inc.
Phone: (808) 529-0866 Fax: (808) 529-0884
http://www.tsdye.com
[-- Attachment #1.2: Type: text/html, Size: 3753 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
reply other threads:[~2009-11-23 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=475706D8-9D64-4427-A44E-3FAA851FD22F@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
/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).