bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Order of command line options handed over to texi2any when running texin


From: Stefan Husmann
Subject: Order of command line options handed over to texi2any when running texinfo-js
Date: Tue, 01 Jan 2019 18:55:20 +0100

Hello list members,

I was trying to genarate html out put of the Emacs Lisp Introduction
using the sources coming with Gnu Emacs from git master. The source file
emacs-lisp-intro.texi uses some files by @including them, which are not
in the same directory, but at ../emacs.

I tried to run

address@hidden lispintro]$ texinfo-js  emacs-lisp-intro.texi
texi2any --html -c EXTRA_HEAD=
<link rel="stylesheet" type="text/css" href="info.css"/>
<script src="modernizr.js" type="text/javascript"></script>
<script src="info.js" type="text/javascript"></script>
 emacs-lisp-intro.texi -o emacs-lisp-intro-html
emacs-lisp-intro.texi:7: @include: docstyle.texi konnte nicht gefunden werden
emacs-lisp-intro.texi:12: @include: emacsver.texi konnte nicht gefunden werden
emacs-lisp-intro.texi:113: warning: undefiniertes Flag: EMACSVER
texinfo-js: texi2any failed

With LANG=C for english output:

address@hidden lispintro]$ LANG=C texinfo-js  emacs-lisp-intro.texi
texi2any --html -c EXTRA_HEAD=
<link rel="stylesheet" type="text/css" href="info.css"/>
<script src="modernizr.js" type="text/javascript"></script>
<script src="info.js" type="text/javascript"></script>
 emacs-lisp-intro.texi -o emacs-lisp-intro-html
emacs-lisp-intro.texi:7: @include: could not find docstyle.texi
emacs-lisp-intro.texi:12: @include: could not find emacsver.texi
emacs-lisp-intro.texi:113: warning: undefined flag: EMACSVER
texinfo-js: texi2any failed

Okay, so I tried

address@hidden lispintro]$ texinfo-js -I ../emacs emacs-lisp-intro.texi
texinfo-js: unknown option --I

Why two hyphens?

This works and produces good looking HTML code:

texinfo-js emacs-lisp-intro.texi -I ../emacs

So the order of options is significant, so far so good. But the error
message is quit unclear.

Happy New Year and best Regards

Stefan Husmann



reply via email to

[Prev in Thread] Current Thread [Next in Thread]