From: Philip Kaludercic <philipk@posteo.net>
To: emacs-orgmode@gnu.org
Subject: Fixing the automatic generation of Tex info node names
Date: Tue, 19 Apr 2022 10:35:26 +0000 [thread overview]
Message-ID: <878rs1tl75.fsf@posteo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
For some reason ox-texinfo removes periods from node names. It seems
this is not necessary as info can render these files without any issues,
and in certain cases not intended (e.g. I had a node named "Emacs 28.1"
and it was abbreviated to "Emacs 281").
This patch should resolve the issue:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-ox-texinfo-Allow-for-periods-in-node-names.patch --]
[-- Type: text/x-diff, Size: 809 bytes --]
From f9a8d9738cb118939a8307bf13f63ec5950bd59b Mon Sep 17 00:00:00 2001
From: Philip Kaludercic <philipk@posteo.net>
Date: Tue, 19 Apr 2022 12:17:40 +0200
Subject: [PATCH] ox-texinfo: Allow for periods in node names
* ox-texinfo.el (org-texinfo--sanitize-node): Don't remove periods
from node names.
---
lisp/ox-texinfo.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ox-texinfo.el b/lisp/ox-texinfo.el
index a01bb268c..3a2c4791b 100644
--- a/lisp/ox-texinfo.el
+++ b/lisp/ox-texinfo.el
@@ -555,7 +555,7 @@ periods, commas and colons."
(replace-regexp-in-string
"[ \t]+" " "
(replace-regexp-in-string
- "[:,.]" ""
+ "[:,]" ""
(replace-regexp-in-string "\\`(\\(.*?)\\)" "[\\1" title)))))
(defun org-texinfo--sanitize-title (title info)
--
2.30.2
[-- Attachment #3: Type: text/plain, Size: 24 bytes --]
--
Philip Kaludercic
next reply other threads:[~2022-04-19 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:35 Philip Kaludercic [this message]
2022-04-19 10:58 ` Fixing the automatic generation of Tex info node names Ihor Radchenko
2022-04-19 11:21 ` Philip Kaludercic
2022-04-20 4:28 ` Ihor Radchenko
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:
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=878rs1tl75.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-orgmode@gnu.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).