From: Ihor Radchenko <firstname.lastname@example.org>
To: Niall Dooley <email@example.com>
Subject: Re: [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument
Date: Thu, 25 May 2023 11:58:23 +0000 [thread overview]
Message-ID: <87lehcwrkw.fsf@localhost> (raw)
Niall Dooley <firstname.lastname@example.org> writes:
>> It would help if you provided more details. Ideally, steps to reproduce
>> the problem. See https://orgmode.org/manual/Feedback.html#Feedback
> I dug a little deeper. `org-tex-info-export-to-info' calls
> `org-texinfo-compile' which in turn calls `org-compile-file'. In this
> function, there is a comment stating "Check for process failure. Output file
> is expected to be located in the same directory as SOURCE." which seems to
> confirm my suspicions that the output .info file is expected to be in the same
> directory as the source .texinfo file. Doing that however, I still get the
> same process "error" as before and the .info file produced in the parent
Which does not help to diagnose the problem, unfortunately.
May you try to reproduce starting from emacs -Q or make repro? See
Essentially, we need to know enough information to see the problem on
our side and understand what the problem is.
> Whilst reading `org-compile-file' I noted the following formatted string
> explains an error I noted in the process error I reported earlier.
> "File %S wasn't produced%s"
> That is this formatted string should be:
> "File %S wasn't produced. %s"
> to avoid the two strings being concatenated together and no punctuation
> separating them.
Fixed, on main.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-05-25 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 14:47 [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument Niall Dooley
2023-05-24 14:59 ` Ihor Radchenko
2023-05-24 18:10 ` Niall Dooley
2023-05-25 11:58 ` Ihor Radchenko [this message]
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).