* Option H: and texinfo export
@ 2013-02-13 19:58 Thomas S. Dye
2013-02-14 17:04 ` Jonathan Leech-Pepin
0 siblings, 1 reply; 2+ messages in thread
From: Thomas S. Dye @ 2013-02-13 19:58 UTC (permalink / raw)
To: Org-mode
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?
These are just questions, not requests for changes to the code. I have
H:4 and things seem to be working beautifully :)
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Option H: and texinfo export
2013-02-13 19:58 Option H: and texinfo export Thomas S. Dye
@ 2013-02-14 17:04 ` Jonathan Leech-Pepin
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Leech-Pepin @ 2013-02-14 17:04 UTC (permalink / raw)
To: Thomas S. Dye; +Cc: Org-mode
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-02-14 17:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-13 19:58 Option H: and texinfo export Thomas S. Dye
2013-02-14 17:04 ` Jonathan Leech-Pepin
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).