From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [PATCH]: ox-latex.eel: handle unnumbered sections in TOC correctly
Date: Sat, 04 Jan 2025 13:09:33 +0000 [thread overview]
Message-ID: <87ikqug1yq.fsf@localhost> (raw)
In-Reply-To: <CAO48Bk_t4ZHMMV7zgnRsgS2Dotw_RkQXNV0MWapzqo+7TiXguQ@mail.gmail.com>
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
> yes, the patch is just a step towards consistency, but I think is is an
> important one, because it
> makes org-mode not generate illegal/faulty LaTeX code.
Right, but it is also kind of half-way between "Org export default" and
"LaTeX" behaviors. If it is expected in LaTeX that unnumbered sections
do not go into TOC, why should ALT_TITLE make them go there? Is it
something expected for LaTeX users?
> As for the photo-finish, I have been thinking the following that we can use
> the 'toc' document property.
>
> Values nil and t work as intended in all backends. This means rewriting
> this part in ox-latex.el.
> Additionally, we add a new value 'toc:latex' to keep the current behaviour
> in ox-latex (at least, other backends could also implement it).
> Coming from the LaTeX world, I lean towards the current ToC handling in
> ox-latex.el (once fixed). It is closer to what I have been doing for the
> last couple of decades ;-)
Depending on the answer to my question above, we may or may not be able
to apply your existing patch right away. I do not yet have a clear
picture what toc:latex should look like -- never put unnumbered headings
into TOC? Only put them when there is ALT_TITLE?
--
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>
prev parent reply other threads:[~2025-01-04 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 17:08 LaTeX export is broken with 'num:nil` and 'ALT_TITLE` Pedro Andres Aranda Gutierrez
2024-12-26 17:15 ` Pedro Andres Aranda Gutierrez
2024-12-27 6:59 ` Pedro Andres Aranda Gutierrez
2024-12-27 17:43 ` Ihor Radchenko
2024-12-27 17:56 ` Pedro Andres Aranda Gutierrez
2024-12-27 18:01 ` Ihor Radchenko
2024-12-27 18:07 ` Pedro Andres Aranda Gutierrez
2024-12-30 7:17 ` Pedro Andres Aranda Gutierrez
2024-12-30 12:44 ` [PATCH]: ox-latex.eel: handle unnumbered sections in TOC correctly Pedro Andres Aranda Gutierrez
2024-12-30 16:53 ` Ihor Radchenko
[not found] ` <CAO48Bk8dXigB0qbXzCuKZK9X4=Woy2+4xpA2QtC4O8Lx_224BA@mail.gmail.com>
2025-01-01 6:43 ` Pedro Andres Aranda Gutierrez
2025-01-01 13:48 ` Ihor Radchenko
2025-01-01 15:48 ` Pedro Andres Aranda Gutierrez
2025-01-02 17:12 ` Ihor Radchenko
2025-01-03 7:10 ` Pedro Andres Aranda Gutierrez
2025-01-04 13:09 ` 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=87ikqug1yq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paaguti@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).