emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>,
	Ihor Radchenko <yantar92@gmail.com>,
	rudolf@adamkovic.org
Subject: Re: PATCH: fix ToC generation in the Latex exporter
Date: Sat, 11 Jan 2025 08:47:15 +0000	[thread overview]
Message-ID: <87seppd9f0.fsf@localhost> (raw)
In-Reply-To: <CAO48Bk9WYFvg1OngdPSuWohh5s0fc+d8LTGBZNH+OZQCx6umUA@mail.gmail.com>

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> Please find attached a patch to fix ToC generation in the LaTeX exporter.
> With this, you don't need to reach back to @@latex @@ constructs to get
> your ToC alright. I have added an option to generate ToC's that is closer
> to LaTeX (num:latex) tha to org

Thanks!

I have been thinking about the consequences of changing the TOC
generation defaults, and my conclusion so far is that we risk breaking
way too many legacy .org documents.

And since old .org documents tend to have "num:t" inside, we cannot rely
upon num:latex returning to the previous behavior.

I think that a more backwards-compatible solution would be creating a
new custom option that will control how ox-latex treats "num:t". By
default, that custom option will keep the old behavior. (This option is
on top of what you have already done).

WDYT?

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2025-01-11  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 16:34 PATCH: fix ToC generation in the Latex exporter Pedro Andres Aranda Gutierrez
2025-01-11  8:47 ` Ihor Radchenko [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=87seppd9f0.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=paaguti@gmail.com \
    --cc=rudolf@adamkovic.org \
    --cc=yantar92@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).