From: 8dcc <8dcc.git@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Can't export variable named "nil" to Texinfo
Date: Sat, 28 Sep 2024 17:08:25 +0200 [thread overview]
Message-ID: <878qvbstna.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Hello,
I can export the following "Variable" to Texinfo with
`org-texinfo-export-to-texinfo':
- Variable: my-name ::
Content...
Results in the following .texi:
@defvar my-name
Content@dots{}
@end defvar
However, if the variable is named "nil" (without the quotes), the
variable name is not exported, and a warning is generated when
processing the .texi file:
- Variable: nil ::
Content...
Results in:
@defvar
Content@dots{}
@end defvar
When running `makeinfo --pdf file.texi':
file.texi:50: warning: missing category for @defvar
I saw the "Variable" to "@defvar" conversion is made with
`org-texinfo--definition-command-alist' in `ox-texinfo.el', which then
gets used in `org-texinfo--match-definition' through the
regexp. However, I was not able to see why a "nil" string isn't
processed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next reply other threads:[~2024-09-28 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 15:08 8dcc [this message]
2024-10-09 16:01 ` [BUG] Can't export variable named "nil" to Texinfo Ihor Radchenko
2024-10-09 17:19 ` 8dcc
2024-10-14 18:43 ` Ihor Radchenko
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=878qvbstna.fsf@gmail.com \
--to=8dcc.git@gmail.com \
--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).