From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: List of figures
Date: Fri, 28 Feb 2014 10:48:13 +0100 [thread overview]
Message-ID: <87txbj600y.fsf@gmx.us> (raw)
In-Reply-To: CAJ51ETrD5=6BCQM2aO2do-bWtqbWoMuYB-Y1UGLvS_6DN81wPA@mail.gmail.com
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> Maybe I am missing something, what would the utility of #+toc: figures be?
> Is it only for export?
>
> I would make a link: [[elisp:org-list-of-figures]] where
> org-list-of-figures is an emacs-lisp function that would parse the buffer
> and present you with a list of clickable links to the figures. You could
> alternatively make this a new org-link, so you could also specify how it
> exports, eg.
>
> [[lof:click-me][List of Figures]]
>
> That would be pure org-markup, and make org more useful, and it would also
> happen to support LaTeX export too. I guess you would recognize figures as
> extensions in the file links.
This is more like org-toc.el, though I'm not sure if it can be
configured to pick up figures.
Using org-element it should be at least be relatively easy to pick up
the structure of the document, though I think the reftex/org-toc way
of displaying such structure is superior to something tied to a
specific line in the buffer (I may want to jump to somewhere from the
bottom of my file).
—Rasmus
--
Got mashed potatoes. Ain't got no T-Bone. No T-Bone
prev parent reply other threads:[~2014-02-28 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 23:28 List of figures Thomas S. Dye
2014-02-23 0:31 ` Rasmus
2014-02-23 17:26 ` Thomas S. Dye
2014-02-23 14:18 ` Nicolas Goaziou
2014-02-23 17:54 ` Thomas S. Dye
2014-02-26 13:50 ` Nicolas Goaziou
2014-02-26 16:37 ` Thomas S. Dye
2014-02-28 1:55 ` John Kitchin
2014-02-28 3:00 ` Thomas S. Dye
2014-03-01 23:22 ` John Kitchin
2014-03-02 8:13 ` Andreas Leha
2014-03-02 15:13 ` John Kitchin
2014-02-28 9:48 ` Rasmus [this message]
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=87txbj600y.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).