From: Ihor Radchenko <yantar92@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: rudolf@adamkovic.org, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`
Date: Fri, 27 Dec 2024 18:01:40 +0000 [thread overview]
Message-ID: <87r05t3szf.fsf@localhost> (raw)
In-Reply-To: <CAO48Bk8ZR_ub5k8MXUc+dSXysA+9S+bDt+Ck8VZqX0KL4tDSkA@mail.gmail.com>
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>> I am slightly concerned about generality of dropping ALT_TITLE from
>> unnumbered sectioning command.
> ...
> I do think we can. Unnumbered sectioning commands never appear in the ToC...
> Unless you use additional magic like, ...
Good. I am not concerned about hacks, I am concerned about users who
customized `org-latex-classes' to use something non-standard for
sectioning.
But if doing so is not expected in general, I'd rather accept your fix
until someone comes and complains. Fixing the existing bug with default
settings is more important than fixing possible bug (affecting less
users) with custom sectioning.
--
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>
next prev parent reply other threads:[~2024-12-27 18:01 UTC|newest]
Thread overview: 9+ 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 [this message]
2024-12-27 18:07 ` Pedro Andres Aranda Gutierrez
-- strict thread matches above, loose matches on Subject: below --
2024-12-25 17:45 Rudolf Adamkovič
2024-12-26 15:08 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r05t3szf.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paaguti@gmail.com \
--cc=rudolf@adamkovic.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.