From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: List of figures
Date: Wed, 26 Feb 2014 06:37:14 -1000 [thread overview]
Message-ID: <m2a9ddq18l.fsf@tsdye.com> (raw)
In-Reply-To: <87k3cit23l.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 26 Feb 2014 14:50:22 +0100")
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
next prev parent reply other threads:[~2014-02-26 16:37 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 [this message]
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
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=m2a9ddq18l.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).