emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Niall Dooley <dooleyn@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-texinfo-export-to-info docstring describes a non-existing optional argument
Date: Wed, 24 May 2023 20:10:32 +0200	[thread overview]
Message-ID: <CADS3Lq5Uv4gK0U93H2EX9r=g43BbhzHT33oXbWVg7bAURmFvFw@mail.gmail.com> (raw)
In-Reply-To: <877csxojvd.fsf@localhost>

On Wed, 24 May 2023 at 16:55, Ihor Radchenko <yantar92@posteo.net> wrote:
> > 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 producedSee "Org INFO Texinfo Output" for details
> 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

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.

  reply	other threads:[~2023-05-24 18:12 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 [this message]
2023-05-25 11:58     ` 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:

  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='CADS3Lq5Uv4gK0U93H2EX9r=g43BbhzHT33oXbWVg7bAURmFvFw@mail.gmail.com' \
    --to=dooleyn@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).