emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
To: emacs-orgmode@gnu.org
Subject: Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Date: Thu, 1 Apr 2021 13:47:02 +0530	[thread overview]
Message-ID: <TY2PR0101MB3693DA652413EA6548970A5ADA7B9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3340 bytes --]

Hello

I am using a Emacs with no custom config.  Here is the version info

Emacs  : GNU Emacs 28.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)

  of 2021-03-20

Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)


When I export the following snippet to TexInfo format the export fails.


** To add a package: (submission, submit)

Adding a basic package is very simple.  There are thorough

instructions below, but the gist of it is that you:

(FWIW, the above snippet is from the README file of Emacs's official 
ELPA repo. cf. 
https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/README#n80)

The error report in *Messages* buffer is

Processing Texinfo file test.texi...

test.texi:4: warning: @settitle missing argument

test.texi:11: warning: @title missing argument

test.texi:23: @menu reference to nonexistent node `(submission'

test.texi:26: warning: node `Top' is up for `To add a package (submission submit)' in sectioning but not in menu

test.texi:18: node `Top' lacks menu item for `To add a package (submission submit)' despite being its Up target

org-compile-file: File "/home/rameshnedunchezian/test.info" wasn’t produced.  See "*Org INFO Texinfo Output*" for details


The error reported in *Org INFO Texinfo Output*  is


test.texi:4: warning: @settitle missing argument

test.texi:11: warning: @title missing argument

test.texi:23: @menu reference to nonexistent node `(submission'

test.texi:26: warning: node `Top' is up for `To add a package (submission submit)' in sectioning but not in menu

test.texi:18: node `Top' lacks menu item for `To add a package (submission submit)' despite being its Up target

This is how test.texi looks like

\input texinfo    @c -*- texinfo -*-
@c %**start of header
@setfilename test.info
@settitle
@documentencoding UTF-8
@documentlanguage en
@c %**end of header

@finalout
@titlepage
@title
@author Ramesh Nedunchezian
@end titlepage

@contents

@ifnottex
@node Top
@top
@end ifnottex

@menu
* To add a package: (submission, submit): To add a package (submission submit).
@end menu

@node To add a package (submission submit)
@chapter To add a package: (submission, submit)

Adding a basic package is very simple.  There are thorough
instructions below, but the gist of it is that you:

@bye

When in texi buffer I do Menu -> TexInfo->Makeinfo buffer, I get the 
same error.  This is not surprising.  Next, I removed the menu entry by 
hand and did Menu->TexInfo->Make Menu.  I get the following input


\input texinfo    @c -*- texinfo -*-

@c %**start of header

@setfilename test.info

@settitle

@documentencoding UTF-8

@documentlanguage en

@c %**end of header

@finalout

@titlepage

@title

@author Ramesh Nedunchezian

@end titlepage

@contents

@ifnottex

@node Top

@top

@end ifnottex



@menu

* To add a package (submission submit)::

@end menu

@node To add a package (submission submit)

@chapter To add a package: (submission, submit)

Adding a basic package is very simple.  There are thorough

instructions below, but the gist of it is that you:

@bye

The above texi output compiles well to info, and the resulting info file 
is browsable.


Looks like the TexInfo exporter may have to take some extra steps when 
there is a 'colon' in the headline text.












[-- Attachment #2: Type: text/html, Size: 4815 bytes --]

             reply	other threads:[~2021-04-01  8:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  8:17 Ramesh Nedunchezian [this message]
2021-04-01 15:16 ` Bug: Error while exporting o TexInfo. Html export works fine. [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)] Nicolas Goaziou
2021-04-02  4:09   ` Ramesh Nedunchezian
2021-04-02 14:50     ` Nicolas Goaziou
2021-04-02  4:33 ` Ramesh Nedunchezian
2021-04-02 14:59   ` Nicolas Goaziou
2021-04-03  4:44     ` Ramesh Nedunchezian
2021-04-03  9:26       ` Nicolas Goaziou
2021-04-03 11:41         ` Ramesh Nedunchezian
2021-04-03 14:40         ` Ramesh Nedunchezian
2021-04-03 14:50           ` Ramesh Nedunchezian
2021-04-03 19:50           ` Nicolas Goaziou
2021-04-04  4:26             ` Ramesh Nedunchezian
2021-04-07 17:59               ` Nicolas Goaziou
2021-04-08 14:00                 ` Ramesh Nedunchezian
2021-04-19  9:30                   ` Nicolas Goaziou

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=TY2PR0101MB3693DA652413EA6548970A5ADA7B9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \
    --to=rameshnedunchezian@outlook.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).