From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: List of figures Date: Sun, 2 Mar 2014 10:13:48 -0500 Message-ID: References: <87y511x67h.fsf@gmail.com> <87k3cit23l.fsf@gmail.com> <8761nx2f3n.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1135eaac2bad0304f3a11e0e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WK85Q-0005jR-Lm for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 10:13:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WK85O-00075L-8O for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 10:13:52 -0500 Received: from mail-pd0-x22d.google.com ([2607:f8b0:400e:c02::22d]:51657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WK85N-00072W-J1 for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 10:13:50 -0500 Received: by mail-pd0-f173.google.com with SMTP id z10so2692217pdj.18 for ; Sun, 02 Mar 2014 07:13:48 -0800 (PST) In-Reply-To: <8761nx2f3n.fsf@med.uni-goettingen.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Andreas Leha Cc: "emacs-orgmode@gnu.org" --001a1135eaac2bad0304f3a11e0e Content-Type: text/plain; charset=ISO-8859-1 No problem. I worked out a List of figures here: http://kitchingroup.cheme.cmu.edu/blog/2014/03/02/Getting-a-list-of-figures-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 Sun, Mar 2, 2014 at 3:13 AM, Andreas Leha < andreas.leha@med.uni-goettingen.de> wrote: > Hi John, > > this is really nice! Thanks for sharing. > > - Andreas > > John Kitchin writes: > > > 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 wrote: > > > > Aloha John, > > > > > > John Kitchin 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 > > wrote: > > > > > >> Aloha Nicolas, > > >> > > >> Nicolas Goaziou 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 > > wrote: > > > > > > Aloha Nicolas, > > > > > > Nicolas Goaziou 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 > > > > > --001a1135eaac2bad0304f3a11e0e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

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

<= /div>

On Sun, Mar 2, 2014 at 3:13 AM, Andreas = Leha <andreas.leha@med.uni-goettingen.de> w= rote:
Hi John,

this is really nice! =A0Thanks for sharing.

- Andreas

John Kitchin <jkitchin@andrew= .cmu.edu> writes:

> check out this implementation for tables:
> http://kitchingroup.ch= eme.cmu.edu/blog/2014/03/01/Getting-a-list-of-tables-in-an-org-buffer/<= br> >
> 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:
>
> =A0 =A0 Aloha John,
>
>
> =A0 =A0 John Kitchin <jk= itchin@andrew.cmu.edu> writes:
>
> =A0 =A0 > Maybe I am missing something, what would the utility of #= +toc:
> =A0 =A0 figures be?
> =A0 =A0 > Is it only for export?
>
>
> =A0 =A0 Yes, it is.
>
>
> =A0 =A0 > I would make a link: [[elisp:org-list-of-figures]] where<= br> > =A0 =A0 > org-list-of-figures is an emacs-lisp function that would = parse
> =A0 =A0 the buffer
> =A0 =A0 > and present you with a list of clickable links to the fig= ures.
> =A0 =A0 You could
> =A0 =A0 > alternatively make this a new org-link, so you could also=
> =A0 =A0 specify how it
> =A0 =A0 > exports, eg.
> =A0 =A0 >
> =A0 =A0 > [[lof:click-me][List of Figures]]
>
>
> =A0 =A0 This is a neat idea. Thanks!
>
> =A0 =A0 All the best,
> =A0 =A0 Tom
>
>
>
> =A0 =A0 >
> =A0 =A0 > That would be pure org-markup, and make org more useful, = and it
> =A0 =A0 would also
> =A0 =A0 > happen to support LaTeX export too. I guess you would rec= ognize
> =A0 =A0 figures as
> =A0 =A0 > extensions in the file links.
> =A0 =A0 >
> =A0 =A0 >
> =A0 =A0 > John
> =A0 =A0 >
> =A0 =A0 > -----------------------------------
> =A0 =A0 > John Kitchin
> =A0 =A0 > Associate Professor
> =A0 =A0 > Doherty Hall A207F
> =A0 =A0 > Department of Chemical Engineering
> =A0 =A0 > Carnegie Mellon University
> =A0 =A0 > Pittsburgh, PA 15213
> =A0 =A0 > 412-2= 68-7803
> =A0 =A0 > http://kitchingroup.cheme.cmu.edu
> =A0 =A0 >
> =A0 =A0 >
> =A0 =A0 >
> =A0 =A0 > On Wed, Feb 26, 2014 at 11:37 AM, Thomas S. Dye <tsd@tsdye.com>
> =A0 =A0 wrote:
> =A0 =A0 >
> =A0 =A0 >> Aloha Nicolas,
> =A0 =A0 >>
> =A0 =A0 >> Nicolas Goaziou <n.goaziou@gmail.com> writes:
> =A0 =A0 >>
> =A0 =A0 >> > Hello,
> =A0 =A0 >> >
> =A0 =A0 >> > tsd@tsdye.com (Thomas S. Dye) writes:
> =A0 =A0 >> >
> =A0 =A0 >> >> I can imagine that a list of figures is a di= fficult problem
> =A0 =A0 in some
> =A0 =A0 >> >> other back-ends. However, its absence in LaT= eX export seems
> =A0 =A0 unusual.
> =A0 =A0 >> >
> =A0 =A0 >> > Org doesn't cover all LaTeX facilities. Ther= e are #+LATEX:
> =A0 =A0 >> > and #+BEGIN_LATEX...#+END_LATEX to fill the gap.=
> =A0 =A0 >> >
> =A0 =A0 >> >> Would it make sense to have this work as exp= ected for LaTeX
> =A0 =A0 export (and
> =A0 =A0 >> >> perhaps other back-ends where it does make s= ense)
> =A0 =A0 >> >
> =A0 =A0 >> > We can start to discuss what a good implementati= on could be
> =A0 =A0 for major
> =A0 =A0 >> > back-ends. But implementing it for LaTeX only is= , IMO, not
> =A0 =A0 worth the
> =A0 =A0 >> > trouble:
> =A0 =A0 >> >
> =A0 =A0 >> > #+toc: figures
> =A0 =A0 >> >
> =A0 =A0 >> > vs.
> =A0 =A0 >> >
> =A0 =A0 >> > #+latex: \listoffigures
> =A0 =A0 >>
> =A0 =A0 >> AFAICT the new exporter works flawlessly. I'm con= fident that it
> =A0 =A0 will
> =A0 =A0 >> let me produce LaTeX to any practical specification.<= br> > =A0 =A0 >>
> =A0 =A0 >> My original query came about because I was trying to = write Org
> =A0 =A0 markup
> =A0 =A0 >> and *not* drop down to LaTeX. In this context--Org as= a
> =A0 =A0 lightweight
> =A0 =A0 >> markup language--the possibility of creating all but = one of the
> =A0 =A0 >> "lists-of" with #+TOC: seems like the marku= p language core is
> =A0 =A0 missing a
> =A0 =A0 >> piece.
> =A0 =A0 >>
> =A0 =A0 >> I look forward to the discussion of implementations f= or the
> =A0 =A0 major
> =A0 =A0 >> back-ends. Let me know if I can help in any way.
> =A0 =A0 >>
> =A0 =A0 >> All the best,
> =A0 =A0 >> Tom
> =A0 =A0 >>
> =A0 =A0 >> --
> =A0 =A0 >> Thomas S. Dye
> =A0 =A0 >> ht= tp://www.tsdye.com
> =A0 =A0 >>
> =A0 =A0 >>
> =A0 =A0 > Maybe I am missing something, what would the utility of #= +toc:
> =A0 =A0 figures
> =A0 =A0 > be? Is it only for export?
> =A0 =A0 >
> =A0 =A0 > I would make a link: [[elisp:org-list-of-figures]] where<= br> > =A0 =A0 > org-list-of-figures is an emacs-lisp function that would = parse
> =A0 =A0 the
> =A0 =A0 > buffer and present you with a list of clickable links to = the
> =A0 =A0 figures.
> =A0 =A0 > You could alternatively make this a new org-link, so you = could
> =A0 =A0 also
> =A0 =A0 > specify how it exports, eg.
> =A0 =A0 >
> =A0 =A0 > [[lof:click-me][List of Figures]]
> =A0 =A0 >
> =A0 =A0 > That would be pure org-markup, and make org more useful, = and it
> =A0 =A0 would
> =A0 =A0 > also happen to support LaTeX export too. I guess you woul= d
> =A0 =A0 recognize
> =A0 =A0 > figures as extensions in the file links.
> =A0 =A0 >
> =A0 =A0 > John
> =A0 =A0 >
> =A0 =A0 > -----------------------------------
> =A0 =A0 > John Kitchin
> =A0 =A0 > Associate Professor
> =A0 =A0 > Doherty Hall A207F
> =A0 =A0 > Department of Chemical Engineering
> =A0 =A0 > Carnegie Mellon University
> =A0 =A0 > Pittsburgh, PA 15213
> =A0 =A0 > 412-2= 68-7803
> =A0 =A0 > http://kitchingroup.cheme.cmu.edu
> =A0 =A0 >
> =A0 =A0 > On Wed, Feb 26, 2014 at 11:37 AM, Thomas S. Dye <tsd@tsdye.com>
> =A0 =A0 wrote:
> =A0 =A0 >
> =A0 =A0 > Aloha Nicolas,
> =A0 =A0 >
> =A0 =A0 > Nicolas Goaziou <n.goaziou@gmail.com> writes:
> =A0 =A0 >
> =A0 =A0 > > Hello,
> =A0 =A0 > >
> =A0 =A0 > > tsd@tsdye.com (= Thomas S. Dye) writes:
> =A0 =A0 > >
> =A0 =A0 > >> I can imagine that a list of figures is a diffic= ult problem
> =A0 =A0 in
> =A0 =A0 > some
> =A0 =A0 > >> other back-ends. However, its absence in LaTeX e= xport seems
> =A0 =A0 > unusual.
> =A0 =A0 > >
> =A0 =A0 > > Org doesn't cover all LaTeX facilities. There ar= e #+LATEX:
> =A0 =A0 > > and #+BEGIN_LATEX...#+END_LATEX to fill the gap.
> =A0 =A0 > >
> =A0 =A0 > >> Would it make sense to have this work as expecte= d for LaTeX
> =A0 =A0 > export (and
> =A0 =A0 > >> perhaps other back-ends where it does make sense= )
> =A0 =A0 > >
> =A0 =A0 > > We can start to discuss what a good implementation c= ould be
> =A0 =A0 for
> =A0 =A0 > major
> =A0 =A0 > > back-ends. But implementing it for LaTeX only is, IM= O, not
> =A0 =A0 worth
> =A0 =A0 > the
> =A0 =A0 > > trouble:
> =A0 =A0 > >
> =A0 =A0 > > #+toc: figures
> =A0 =A0 > >
> =A0 =A0 > > vs.
> =A0 =A0 > >
> =A0 =A0 > > #+latex: \listoffigures
> =A0 =A0 >
> =A0 =A0 > AFAICT the new exporter works flawlessly. I'm confide= nt that it
> =A0 =A0 > will
> =A0 =A0 > let me produce LaTeX to any practical specification.
> =A0 =A0 >
> =A0 =A0 > My original query came about because I was trying to writ= e Org
> =A0 =A0 > markup
> =A0 =A0 > and *not* drop down to LaTeX. In this context--Org as a > =A0 =A0 > lightweight
> =A0 =A0 > markup language--the possibility of creating all but one = of the
> =A0 =A0 > "lists-of" with #+TOC: seems like the markup la= nguage core is
> =A0 =A0 > missing a
> =A0 =A0 > piece.
> =A0 =A0 >
> =A0 =A0 > I look forward to the discussion of implementations for t= he
> =A0 =A0 major
> =A0 =A0 > back-ends. Let me know if I can help in any way.
> =A0 =A0 >
> =A0 =A0 > All the best,
> =A0 =A0 > Tom
> =A0 =A0 >
> =A0 =A0 > --
> =A0 =A0 > Thomas S. Dye
> =A0 =A0 > http:/= /www.tsdye.com
> =A0 =A0 >
> =A0 =A0 >
> =A0 =A0 >
>
> =A0 =A0 --
> =A0 =A0 Thomas S. Dye
> =A0 =A0 http://www.= tsdye.com
>



--001a1135eaac2bad0304f3a11e0e--