emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Fixing the automatic generation of Tex info node names
Date: Wed, 20 Apr 2022 12:28:00 +0800	[thread overview]
Message-ID: <87lew0z8dr.fsf@localhost> (raw)
In-Reply-To: <874k2ptj1z.fsf@posteo.net>

Philip Kaludercic <philipk@posteo.net> writes:

> Would you happen to know what the issue is?  As I said, the documents
> appear to render just as expected in my case, but it might just be due
> to the version or because I didn't hit some specific edge-case.

The link I shared is all I know. Apparently, using some symbols in node
names is discouraged by texinfo manual exactly because it can break some
edge cases. The recommendation is replacing those symbols with texinfo
commands, which is less discouraged.

Probably, the right way to approach this issue is using texinfo commands
to insert [.,:] and also issuing a warning during export.


  reply	other threads:[~2022-04-20  4:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 10:35 Fixing the automatic generation of Tex info node names Philip Kaludercic
2022-04-19 10:58 ` Ihor Radchenko
2022-04-19 11:21   ` Philip Kaludercic
2022-04-20  4:28     ` Ihor Radchenko [this message]
2022-05-04 22:52     ` TRS-80

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:

  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=87lew0z8dr.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=philipk@posteo.net \


* 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


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).