From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <rudolf@adamkovic.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH v3] Improvements to Texinfo exporter (was: [PATCH] Re: Texinfo: Custom navigation and links in headings)
Date: Sat, 31 Aug 2024 13:36:47 +0000 [thread overview]
Message-ID: <877cbwn79s.fsf@localhost> (raw)
In-Reply-To: <m2v7zi173n.fsf@adamkovic.org>
Rudolf Adamkovič <rudolf@adamkovic.org> writes:
> I found I do not need alternative navigation, as I can simulate
> "alternative up" with links in parent Org headings.
>
> [Texinfo renders that just fine in HTML.]
>
> The other two patches are bug fixes, to
>
> - support links in headings
> (including those exported as lists)
>
> and
>
> - support numeric `toc:' values in `#+OPTIONS'
> (like an export backend should),
>
> which are important.
>
> I will rebase those onto `main' and
>
> submit them separately,
>
> one per thread, to
>
> make code review easier.
Ok.
Closing this thread.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
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-08-31 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 18:20 Texinfo: Custom navigation and links in headings Rudolf Adamkovič
2024-08-23 7:08 ` Rudolf Adamkovič
2024-08-23 12:45 ` Rudolf Adamkovič
2024-08-24 6:46 ` [PATCH] Re: Texinfo: Custom navigation and links in headings (was: Texinfo: Custom navigation and links in headings) Rudolf Adamkovič
2024-08-24 9:19 ` [PATCH] Re: Texinfo: Custom navigation and links in headings Rudolf Adamkovič
2024-08-24 19:54 ` [PATCH v3] Improvements to Texinfo exporter (was: [PATCH] Re: Texinfo: Custom navigation and links in headings) Rudolf Adamkovič
2024-08-30 13:19 ` Rudolf Adamkovič
2024-08-31 13:36 ` Ihor Radchenko [this message]
2024-08-31 20:48 ` Rudolf Adamkovič
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=877cbwn79s.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--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 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).