From: John Kitchin <jkitchin@andrew.cmu.edu>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: List of figures
Date: Sat, 1 Mar 2014 18:22:36 -0500 [thread overview]
Message-ID: <CAJ51ETpE1+-mjUapN+2syyiPjqh1SDFwbXcFdtVqnRtmWwyHyQ@mail.gmail.com> (raw)
In-Reply-To: <m2sir42b6j.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 5898 bytes --]
check out this implementation for tables:
http://kitchingroup.cheme.cmu.edu/blog/2014/03/01/Getting-a-list-of-tables-in-an-org-buffer/
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Thu, Feb 27, 2014 at 10:00 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha John,
>
> 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?
>
> Yes, it is.
>
> > 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]]
>
> This is a neat idea. Thanks!
>
> All the best,
> Tom
>
> >
> > 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.
> >
> >
> > John
> >
> > -----------------------------------
> > John Kitchin
> > Associate Professor
> > Doherty Hall A207F
> > Department of Chemical Engineering
> > Carnegie Mellon University
> > Pittsburgh, PA 15213
> > 412-268-7803
> > http://kitchingroup.cheme.cmu.edu
> >
> >
> >
> > On Wed, Feb 26, 2014 at 11:37 AM, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> >> Aloha Nicolas,
> >>
> >> Nicolas Goaziou <n.goaziou@gmail.com> writes:
> >>
> >> > Hello,
> >> >
> >> > tsd@tsdye.com (Thomas S. Dye) writes:
> >> >
> >> >> I can imagine that a list of figures is a difficult problem in some
> >> >> other back-ends. However, its absence in LaTeX export seems unusual.
> >> >
> >> > Org doesn't cover all LaTeX facilities. There are #+LATEX:
> >> > and #+BEGIN_LATEX...#+END_LATEX to fill the gap.
> >> >
> >> >> Would it make sense to have this work as expected for LaTeX export
> (and
> >> >> perhaps other back-ends where it does make sense)
> >> >
> >> > We can start to discuss what a good implementation could be for major
> >> > back-ends. But implementing it for LaTeX only is, IMO, not worth the
> >> > trouble:
> >> >
> >> > #+toc: figures
> >> >
> >> > vs.
> >> >
> >> > #+latex: \listoffigures
> >>
> >> AFAICT the new exporter works flawlessly. I'm confident that it will
> >> let me produce LaTeX to any practical specification.
> >>
> >> My original query came about because I was trying to write Org markup
> >> and *not* drop down to LaTeX. In this context--Org as a lightweight
> >> markup language--the possibility of creating all but one of the
> >> "lists-of" with #+TOC: seems like the markup language core is missing a
> >> piece.
> >>
> >> I look forward to the discussion of implementations for the major
> >> back-ends. Let me know if I can help in any way.
> >>
> >> All the best,
> >> Tom
> >>
> >> --
> >> Thomas S. Dye
> >> http://www.tsdye.com
> >>
> >>
> > 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.
> >
> > John
> >
> > -----------------------------------
> > John Kitchin
> > Associate Professor
> > Doherty Hall A207F
> > Department of Chemical Engineering
> > Carnegie Mellon University
> > Pittsburgh, PA 15213
> > 412-268-7803
> > http://kitchingroup.cheme.cmu.edu
> >
> > On Wed, Feb 26, 2014 at 11:37 AM, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> > Aloha Nicolas,
> >
> > Nicolas Goaziou <n.goaziou@gmail.com> writes:
> >
> > > Hello,
> > >
> > > tsd@tsdye.com (Thomas S. Dye) writes:
> > >
> > >> I can imagine that a list of figures is a difficult problem in
> > some
> > >> other back-ends. However, its absence in LaTeX export seems
> > unusual.
> > >
> > > Org doesn't cover all LaTeX facilities. There are #+LATEX:
> > > and #+BEGIN_LATEX...#+END_LATEX to fill the gap.
> > >
> > >> Would it make sense to have this work as expected for LaTeX
> > export (and
> > >> perhaps other back-ends where it does make sense)
> > >
> > > We can start to discuss what a good implementation could be for
> > major
> > > back-ends. But implementing it for LaTeX only is, IMO, not worth
> > the
> > > trouble:
> > >
> > > #+toc: figures
> > >
> > > vs.
> > >
> > > #+latex: \listoffigures
> >
> > AFAICT the new exporter works flawlessly. I'm confident that it
> > will
> > let me produce LaTeX to any practical specification.
> >
> > My original query came about because I was trying to write Org
> > markup
> > and *not* drop down to LaTeX. In this context--Org as a
> > lightweight
> > markup language--the possibility of creating all but one of the
> > "lists-of" with #+TOC: seems like the markup language core is
> > missing a
> > piece.
> >
> > I look forward to the discussion of implementations for the major
> > back-ends. Let me know if I can help in any way.
> >
> > All the best,
> > Tom
> >
> > --
> > Thomas S. Dye
> > http://www.tsdye.com
> >
> >
> >
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
[-- Attachment #2: Type: text/html, Size: 8570 bytes --]
next prev parent reply other threads:[~2014-03-01 23:22 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 [this message]
2014-03-02 8:13 ` Andreas Leha
2014-03-02 15:13 ` John Kitchin
2014-02-28 9:48 ` Rasmus
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=CAJ51ETpE1+-mjUapN+2syyiPjqh1SDFwbXcFdtVqnRtmWwyHyQ@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=tsd@tsdye.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).