From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Option H: and texinfo export
Date: Thu, 14 Feb 2013 12:04:08 -0500 [thread overview]
Message-ID: <CAEWDx5dNPGCXr2PGxx0AHGfBPdUvpTdeLw1sHtZ2UgQPBzCVxA@mail.gmail.com> (raw)
In-Reply-To: <m1ip5wrno9.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
Hello Tom
On 13 February 2013 14:58, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha all,
>
> When the H: option is set to a number > 4, the texinfo exporter
> generates a detailed node listing with links to nodes that texinfo
> doesn't recognize. IIUC, texinfo recognizes nodes for chapter, section,
> subsection, and subsubsection, but not for any lower level divisions of
> the document.
>
> Is there a context where H:5..n would make sense in a document exported
> to texinfo? If not, should the exporter behave differently in this
> instance?
>
I don't know of any case where there would be a reason to have n>4 for
headline export to texinfo.
> These are just questions, not requests for changes to the code. I have
> H:4 and things seem to be working beautifully :)
>
I've made a small change regardless, a constant with the max toc-depth
for texinfo (4), in case there ever is a time in the future where this depth
might have reason to change. I've also set the detailed node listing to
limit
itself to whichever value is smaller (H: or 4). This should prevent any
accidental generation errors due to H being too large.
Regards,
Jon
--
> All the best,
> Tom
>
> --
> T.S. Dye & Colleagues, Archaeologists
> 735 Bishop St, Suite 315, Honolulu, HI 96813
> Tel: 808-529-0866, Fax: 808-529-0884
> http://www.tsdye.com
>
>
[-- Attachment #2: Type: text/html, Size: 2189 bytes --]
prev parent reply other threads:[~2013-02-14 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 19:58 Option H: and texinfo export Thomas S. Dye
2013-02-14 17:04 ` Jonathan Leech-Pepin [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=CAEWDx5dNPGCXr2PGxx0AHGfBPdUvpTdeLw1sHtZ2UgQPBzCVxA@mail.gmail.com \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).