From: Niall Dooley <firstname.lastname@example.org>
Subject: [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument
Date: Wed, 24 May 2023 16:47:02 +0200 [thread overview]
Message-ID: <CADS3Lq7W=LZYd3F3aA0p1RaDWdHSmwahvs8oyJfx_Hw0WF9K9Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
The `org-texinfo-export-to-info' docstring describes a non-existing optional
argument PUB-DIR but no such argument is given in the definition. Perhaps
did in the past?
Aside, when invoking this command on an org file I get the following error
which may or not be a bug also:
org-compile-file: File "<path-to-repository>/org-gtd.el/doc/org-gtd.info"
wasn’t produced See "Org INFO Texinfo Output" for details
The strange thing is the INFO file is produced (or rather updated as it
existed) and the output buffer is empty. The INFO file resides in the
directory above the one that contains the org and texinfo files. The error
states it is not produced in the directory where the org and texinfo files
reside so perhaps unsurprising if it already exists in the parent directory.
Should they all reside in the same directory perhaps?
Thanks for Org and your time.
[-- Attachment #2: Type: text/html, Size: 1050 bytes --]
next reply other threads:[~2023-05-24 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 14:47 Niall Dooley [this message]
2023-05-24 14:59 ` [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument Ihor Radchenko
2023-05-24 18:10 ` Niall Dooley
2023-05-25 11:58 ` Ihor Radchenko
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 \
* 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).