[help-texinfo] Inserting text in tex math mode
I have the following tex contruct and want to add text inside the math _expression_,
for example adding
i.e. if
before \exists. However I am not sure how to tell texinfo to write this
as text mode within math _expression_.
@tex
$$ \exists \ s \ :: \
n(a^{tlv}_{s1},a^{tlv}_{s2},a^{tlv}_{s3}) \geq 2 $$
@end tex
[help-texinfo] Underfull
I am tryiong to make a horizontal line in my document using the following
@noindent @center {
--}
This creates the following when using texi2pdf
Underfull \hbox (badness 1) in paragraph at lines
How may I resolve this problem?
[help-texinfo] Section Numbering
@chapter GNU Free Documentation License @unnumberedsec 0 PREAMBLE @section APPLICABILITY AND DEFINITIONS @section VERBATIM COPYING @section COPYING IN QUANTITY I want PREAMBLE to start at zero, however the next section starts at 4.2 rather than 4.1 How can I fix this problem? 4 GNU Free Documentation License . . . . . . . . . . . . 7 0 PREAMBLE . . . . . . . . . . . . . . . . . . . . . . 7 4.2 APPLICABILITY AND DEFINITIONS . . . . . . . . . . 7 4.3 VERBATIM COPYING . . . . . . . . . . . . . . . . . 9 - Christopher Dimech GNU Behistun Chief Administrator - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Exploitation
[help-texinfo] Using @table with @smalldisplay
Dear hackers,
I want to create a table in small font, however when I use @smalldisplay or
@smallformat, the description of each variable consists as though I am using
@verbatim, where the output text of the environment is exactly as is (in the
fixed-width font). Is there any way to solve this problem so the description
looks like a paragraph?
@table @var
@smalldisplay
@item repository
The @var{repository} argument gives a directory name, or a path to
a directory, under the CVS root directory for repositories; if the
directory did not exist, @var{import} creates it. A directory of
that name gets created in the repository. The name identifies the
collection of source code, the name under which you CheckOut the
WorkingCopy from the repository.
@item packagetag
The @code{packagetag} is a tag for the entire branch.
@item releasetag
The @var{releasetag} uniquely identifies the files at the leaves
created each time you execute @code{import}. The @var{releasetag}
should be new, not previously existing in the repository file, and
uniquely identify the imported release.
@end smalldisplay
@end table
-
Christopher Dimech
GNU Behistun Chief Administrator
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Exploitation
[help-texinfo] Using @ref @xref and @pxref
I have written a document in texinfo. I put all the document material into one
file.
Now I am trying to split things into multiple files as the document has become
too long.
I have seen that @ref can be used with up to five parameters but cannot find
useful examples
of how to carry out the change. I would appreciate help in this new plan so
very much
$ ~/umedu
.
├── report.texi
├── chap1
│ ├── bibliography.texi
│ ├── figures.texi
└── umedu--files
Here are examples I had using @ref
report.texi:
@pxref{fig:siculo--calabri--tectonic--map}.
@ref{gutscher--kopp--krastel--et--al--2017,, Marc-Andr@'e (2017)}
@node figures
@unnumberedsec Figures
@include ./chap1/figures.texi
@node bibliography
@unnumberedsec Bibliography
@include ./chap1/bibliography.texi
figures.texi:
@float Figure,fig:siculo--calabri--tectonic--map
@center @image{./umedu--files/siculo--calabri--tectonic--map,11cm,,,.png}
@caption{Description}
@shortcaption{Short Description}
@end float
bibliography.texi:
@anchor{gutscher--kopp--krastel--et--al--2017}
2017. @sc{Gutscher, Marc-Andr@'e}; @strong{Active tectonics of
the Calabrian subduction revealed by new multi-beam bathymetric data and
high-resolution seismic profiles in the Ionian Sea (Central
Mediterranean).} Earth and Planetary Science Letters, Volume 461,
Pagination 61-72.
@uref{https://www.researchgate.net/Calabrian_subduction_revealed, [Complete
Article]}.
@c {Published: January 09}
[help-texinfo] User defined sectioning numbers when using @unnumbered
Dear Compeers, I am using an @unnumbered chapter so it displays in the contents section when I call @contents. Is there any way to add section numbers such as @unnumbered 1 Preamble @unnumberedsec 1.1 Applicability and Definitions @unnumberedsubsec 1.1.1 Verbatim Copying However, rather than hardwiring the sectioning numerical sequence (e.g., 1, 1.1, 1.1.1, ...etc), is it possible to define some variables in another file and they then get replaced at the beginning of the @unnumbered @unnumberedsec and @unnumberedsubsec names? Define label--preamb, label--appldef, label--verbatim in some top level file top--level--document.texi: @page @node license--unnumbered @unnumbered label--license License @include ./license--unnumbered.texi license--unnumbered.texi: @unnumberedsec label--preamb Preamble @unnumberedsec label--appldef Applicability and Definitions @unnumberedsec label--copying Verbatim Copying @unnumberedsubsec label--cpinq Copying in Quantity
Re: [help-texinfo] User defined sectioning numbers when using @unnumbered
The reason is that I am writing a book. Each chapter has an appendix section.
In summary, an appendix needs to relate directly to the subject. In addition,
I aim to have chapters only about the topics I wish to discuss.
Consequently, any License and Copyright Documents would use a different
numbering
sequence different than for chapters or appendices.
Naturally, I also have separate License and Copyright Documents sectioned as
chapter and appendices too so I may use them as necessary in other documents
I write.
For the @unnumbered version, I would need a way to define the sectioning format
so I can use them in different documents, but at the same time I can use the
same @include ./license--unnumbered.texi This means that different documents
can have different sectioning even though they may call the same
./license--unnumbered.texi
├── freelic
│ ├── cc
│ └── gnu
│ ├── agpl--chapter.texi
│ ├── agpl--appendix.texi
│ ├── agpl--unnumbered.texi
│ ├── gfdl--chapter.texi
│ ├── gfdl--appendix.texi
│ └── gfdl--unnumbered.texi
> Sent: Wednesday, January 02, 2019 at 7:05 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: help-texinfo@gnu.org
> Subject: Re: [help-texinfo] User defined sectioning numbers when using
> @unnumbered
>
> On Wed, Jan 02, 2019 at 06:32:33PM +0100, Christopher Dimech wrote:
> > Dear Compeers,
> >
> > I am using an @unnumbered chapter so it displays in the contents section
> > when I call @contents. Is there any way to add section numbers such as
>
> I don't understand why you don't just use @chapter or @appendix instead
> of @unnumbered if you want the chapter to be numbered.
>
> > Define label--preamb, label--appldef, label--verbatim in some top level file
>
> Possibly with
>
> @set label--preamb 1.2.3
>
> then refer to it with @value{label--preamb}. However, there is a
> chance this won't work when processed with TeX.
>
> > top--level--document.texi:
> > @page
> > @node license--unnumbered
> > @unnumbered label--license License
> > @include ./license--unnumbered.texi
> >
> > license--unnumbered.texi:
> > @unnumberedsec label--preamb Preamble
> > @unnumberedsec label--appldef Applicability and Definitions
> > @unnumberedsec label--copying Verbatim Copying
> > @unnumberedsubsec label--cpinq Copying in Quantity
> >
> >
> >
>
Re: [help-texinfo] Calling User Defined functions
I think I have made a mistake. What I want to do is call the following
thing everytime by just passing the parameters.
@float Figure,fig-208-2051
@center @image{@value{imgnm},@value{imgsz},,,.png}
@caption{@value{explan}
@flushright
@* Label: @t{@value{fignm}}
@c Return to @ref{identification--of--hazards,, @value{idh}}.
@end flushright
}
@shortcaption{@value{shtc}.}
@end float
Is there any simpler way to call the same sequence of commands but using
just different parameters for me to display many figures?
> Sent: Thursday, May 30, 2019 at 5:08 PM
> From: "Christopher Dimech"
> To: "help-texinfo gnu"
> Subject: [help-texinfo] Calling User Defined functions
>
> I have produced a simple function put I do not know how to use it.
> Tried checking the manual but have not been able to find where it
> mentions how user define functions can be used.
>
> @deffn Command disp-expr imgnm
> The name of the image is @var{imgnm}
> @end deffn
>
>
[help-texinfo] Calling User Defined functions
I have produced a simple function put I do not know how to use it.
Tried checking the manual but have not been able to find where it
mentions how user define functions can be used.
@deffn Command disp-expr imgnm
The name of the image is @var{imgnm}
@end deffn
Re: [help-texinfo] Calling User Defined functions
I think a macro would do the trick and have been trying
The image is not showing up and I am getting an error.
@macro dispimg {imgnm}
File Name: \imgnm\
@center @image{\imgnm\,10cm,,,.png}
@end macro
@set imgnm ./q208--files/208--2051
@dispimg{@value{imgnm}}
> Sent: Thursday, May 30, 2019 at 5:36 PM
> From: "Christopher Dimech"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: [help-texinfo] Calling User Defined functions
>
>
> I think I have made a mistake. What I want to do is call the following
> thing everytime by just passing the parameters.
>
>
> @float Figure,fig-208-2051
> @center @image{@value{imgnm},@value{imgsz},,,.png}
> @caption{@value{explan}
> @flushright
> @* Label: @t{@value{fignm}}
> @c Return to @ref{identification--of--hazards,, @value{idh}}.
> @end flushright
> }
> @shortcaption{@value{shtc}.}
> @end float
>
> Is there any simpler way to call the same sequence of commands but using
> just different parameters for me to display many figures?
>
>
>
>
> > Sent: Thursday, May 30, 2019 at 5:08 PM
> > From: "Christopher Dimech"
> > To: "help-texinfo gnu"
> > Subject: [help-texinfo] Calling User Defined functions
> >
> > I have produced a simple function put I do not know how to use it.
> > Tried checking the manual but have not been able to find where it
> > mentions how user define functions can be used.
> >
> > @deffn Command disp-expr imgnm
> > The name of the image is @var{imgnm}
> > @end deffn
> >
> >
>
Re: [help-texinfo] Texi documents in double spacing
Yes, that works. However, I was thinking on double-spacing the whole
document rather than just the areas between the "@tex" and "@end tex"
structure.
Could not find such details in the texinfo manual for a command
that introduces double spacing that I can call before @title.
I used to think that I need to call \baselinefactor or \baselineskip
everytime I call the @tex structure, but have seen that the command
is applied whenever I call the @tex struct.
Have also noticed that I can use the texinfo @-command inside the @tex
structure. By this I mean that the @tex structure does not impose the
use of only tex \-commands, but also texinfo @-commands such as @emph{}
as well.
Christopher
> Sent: Sunday, May 12, 2019 at 6:54 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: [help-texinfo] Texi documents in double spacing
>
> On 5/12/19, Christopher Dimech wrote:
> > I am writing a book using texinfo. Anyway I can make text double spaced? I
> > have looked at the manula but noticed nothing specific. I can do double
> > spacing in sections within "@tex" and "@end tex".
>
> I am not completely sure of all the details but
>
> @tex
> \gdef\baselinefactor{2}%
> \letterpaper
> @end tex
>
> appears to work to produce double spacing in all following material.
>
> (I also discovered a bug while testing this in that \globaldefs=1
> inside @tex leaves the catcode of newline as active, contrary to what
> is stated in the manual.)
>
[help-texinfo] Texi documents in double spacing
I am writing a book using texinfo. Anyway I can make text double spaced? I have looked at the manula but noticed nothing specific. I can do double spacing in sections within "@tex" and "@end tex". Christopher
Re: [help-texinfo] Cross-References display undefined when using @include
This is a basic test composed of two files "2019308.texi" (main with
cross-references) and
"bibl.texi" (bibliography with an anchor).
Cross-References do work (when one clicks on the reference, it directs you to
the cross-reference).
However the pdf file shows
[bibl-Semenza-et-Ghirotti-2000], page
However when one uses @setfilename 2019308.info (comment the line out), one gets
[bibl-Semenza-et-Ghirotti-2000], page 2
Have been under the impression that if there is no @setfilename line, makeinfo
uses the
input file name to determine the output name. Was aware that @setfilename used
to be
required by the Texinfo processors, but I've read it is no longer
required.However, this
test shows otherwise.
Christopher
Details of the files appear below
cat 2019308.texi
\input texinfo
@c @setfilename 2019308.info
@settitle 2019308
@smallbook
@titlepage
@title @sc{bug-texinfo 2019308}
@author Christopher Dimech
@end titlepage
@contents
@node executive-summary
@unnumbered E @ @ Executive Summary
Let us make a reference to the article by Semenza and Ghirotti.
Try using the reference @ref{bibl-Semenza-et-Ghirotti-2000}
@page
@node umrq30801
@unnumbered 01 Bibliography
@include ./2019308--txfiles/bibl.texi
@bye
cat bibl.texi
@paragraphindent 0
@sp 1
@anchor{bibl-Semenza-et-Ghirotti-2000}
2000.@: @sc{Semenza, Edoardo}; Ghirotti, Monica; @strong{History of 1963 Vaiont
Slide. The importance of the geological factors to recognise the
ancient landslide.} Bulletin of Engineering Geology and the
Environment, Issue 59, Pages 87-97.
@uref{http://www.ukm.my/zuhairi/Pengajaran/intranet/stag3072/reading%20materials/VAIONT%20DAM%20in%20Italy_geologic%20factor.pdf,,
[@sc{Complete Article}]}. [@t{bibl-Semenza-et-Ghirotti-2000}]
@c Published: April 04
@paragraphindent 1
---------
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Friday, July 12, 2019 at 8:43 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: [help-texinfo] Cross-References display undefined when using
> @include
>
> On Fri, Jul 12, 2019 at 05:40:56PM +0200, Christopher Dimech wrote:
> > Dear Compeers,
> >
> > I have written a bibliography chapter in file "bibl.texi"
> >
> > Then I included "bibl.texi" in my main file "umrq.texi", and included
> > cross-references
> > to anchors defined in "bibl.texi".
> >
> > Running "texi2pdf umrq.texi", I have noticed that cross-references in the
> > main text
> > show as undefined. Yet when I place the cursor on the cross-reference the
> > page number
> > is correct and when I click on the cross-reference, the link gets me
> > directly to the
> > correct bibliography item.
>
> I wonder if it is related to the other problem you reported with
> @listoffloats as included files are being used and the cross-references
> and floats are both listed in the auxiliary *.aux file, e.g. umrq.aux.
> Can you try and create a minimal failling example and send it to this
> list?
>
[help-texinfo] Using @image with @value gives an error
I have noticed that the following commands works well
@center @image{../umrq3--files/E--ExecSm/309E--a01,11cm,,,.png}
However the following one gives an error
@set upath ../umrq3--files/E--ExecSm
@center @image{@value{upath}/309E--a01,11cm,,,.png}
[help-texinfo] Using @ref with two arguments
I am getting quite confused on why would need @ref with two arguments.
Could not find an example when using two arguments is useful when using
texi2pdf.
Then
@ref{ccby--oth--rights}
This prints Section 1.1.2 [ccby--oth--rights]
@ref{ccby--scope, ccby--oth--rights}
This prints Section 1.1 [ccby--scope]
Is there a way to print the following
Section 1.1.2 [d]
but the reference gets you at the anchor point rather
than to Section 1.1.2?
I am using texi2pdf.
The sectioning is as follows
@node free-lic
@chapter Free License
@node ccby--scope
@section Scope
@node ccby--lic--grant
@subsection License Grant
@node ccby--oth--rights
@subsection Other Rights
@enumerate a
@item Text
@item Text
@item Text
@anchor{ccby--pattm--rights}
@item Text
@end enumerate
Re: [help-texinfo] Cross-References display undefined when using @include
I removed all the files, and rerun texi2pdf 2019308.texi Still, I get undefined. Still haven't figured out how this is happening. when I use @setfilename and run texi2pdf a few times, everything is correct. - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Monday, July 15, 2019 at 11:52 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: [help-texinfo] Cross-References display undefined when using > @include > > On Sat, Jul 13, 2019 at 12:38:09AM +0200, Christopher Dimech wrote: > > This is a basic test composed of two files "2019308.texi" (main with > > cross-references) and > > "bibl.texi" (bibliography with an anchor). > > > > Cross-References do work (when one clicks on the reference, it directs you > > to the cross-reference). > > However the pdf file shows > > [bibl-Semenza-et-Ghirotti-2000], page > > > > However when one uses @setfilename 2019308.info (comment the line out), one > > gets > > [bibl-Semenza-et-Ghirotti-2000], page 2 > > > > Have been under the impression that if there is no @setfilename line, > > makeinfo uses the > > input file name to determine the output name. Was aware that @setfilename > > used to be > > required by the Texinfo processors, but I've read it is no longer > > required.However, this > > test shows otherwise. > > @setfilename is not used at all when processing with TeX. The most > likely explanation is that the auxiliary files changed between runs of > TeX. If you had processed the file again *without* commenting out the > @setfilename line, then I expect the cross-reference would also have > been output correctly. > > I tested it both with "texi2pdf 2019308.texi" and "makeinfo --pdf > 2019308.texi" and both times TeX is run twice as it should be. > > If you run "pdfetex 2019308.texi" just once when 2019308.aux and > 2019308.toc don't exist, then the output is what you got. > > What exactly are you doing to process the files? >
Re: [help-texinfo] Using @ref with two arguments
In what context do you use the second argument and what does it do exactly? As Patrice said it does nothing for pdf. My understanding is that one uses it for display purposes and not for directing to a node or an anchor. > Sent: Monday, July 22, 2019 at 5:25 PM > From: "Eli Zaretskii" > To: "Patrice Dumas" > Cc: dim...@gmx.com, help-texinfo@gnu.org > Subject: Re: [help-texinfo] Using @ref with two arguments > > > Date: Mon, 22 Jul 2019 16:49:50 +0200 > > From: Patrice Dumas > > Cc: help-texinfo gnu > > > > in general I would suggest not using an @*ref command with a non > > empty second argument. > > I don't understand why. FWIW, I use it quite a lot, and find it very > useful. >
Setting Page Size and displaying result correctly
Dear Compeers, I have recently mentioned allowing multiline titles in structured commands (e.g. @chapter, @section, @unnumberedsec) Another Texinfo aspect to mention is properly setting the page size using @pagesizes. Firstly, if one uses a smaller pagesize, the resulting pdf simply cuts the page out to the required size. This means that the part of the text, figures, etc ... that is outside the area are cut out. Have used @pagesizes 250mm,176mm I have also noticed that the result is almost correct, showing a pagesize of 250mm,182mm. Perhaps it is also something to look at. Making @pagesizes work would be extremely beneficial for users. Regards Christopher
@ifset at Line Beginning and @menu after sectioning calls
Dear Compeers, Customarily the texinfo structures for my manuals get quite complicated. Consequently, I point out two things. 1. @ifset @ifclear have only appear at a line beginning 2. @menu cannot occur after every sectioning label @section @subsection @heading @unnumbered Comments: 1. @ifset should allow indentation like many other commands 2. A menu should be allowed to display itself after section commands In my intro file I have added a menu after @chapter and before the first @section I put the menu in a macro, then I simply call the macro @Gela-. --- Top Level File: 00-gungadin-elisp-abbrev \input texinfo etc @menu * Introduction:: Introduction to Emacs Lisp. @detailmenu Subnodes so you can view them easily in one step: Introduction * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end detailmenu @end menu @ifset Volume-1 @include 01-gela-intro.texi @end ifset @bye --- Intro File: 01-gela-intro.texi @macro Gela-Menu @menu * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end menu @end macro @node Introduction @chapter Introduction Introduction Text @chapter CTitle @section First Section @Gela-Menu @subsection First SubSection @section Second Section @Gela-Menu Regards Christopher
@ifset at Line Beginning and @menu after sectioning calls
Continuing some more regarding @menu. Normally, when you view an info file, the first line shows where you are located For instance (gungadin-elisp-abbrev)Top > Introduction > Modifier Keys It is great and I love it. It would be better still if this is also displayed at the bottom after one has finished scrolling down. With this additional thing reading would be super. Regards C* Dear Compeers, Customarily the texinfo structures for my manuals get quite complicated. Consequently, I point out two things. 1. @ifset @ifclear have only appear at a line beginning 2. @menu cannot occur after every sectioning label @section @subsection @heading @unnumbered Comments: 1. @ifset should allow indentation like many other commands 2. A menu should be allowed to display itself after section commands In my intro file I have added a menu after @chapter and before the first @section I put the menu in a macro, then I simply call the macro @Gela-. --- Top Level File: 00-gungadin-elisp-abbrev \input texinfo etc @menu * Introduction:: Introduction to Emacs Lisp. @detailmenu Subnodes so you can view them easily in one step: Introduction * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end detailmenu @end menu @ifset Volume-1 @include 01-gela-intro.texi @end ifset @bye --- Intro File: 01-gela-intro.texi @macro Gela-Menu @menu * Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards. * Key-Mnemonics:: Mnemonics that identify specific keys. * Composing-KeySeq:: Composing Key Sequences. * Complete-Kbd:: Complete Key Bindings. * Docu-KeySeq:: Documentationm of Key Sequences. * Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww. * Docu-Function:: Documentation of Functions. * Intactv-Function:: Interactive Functions. * UPrefix-Argument:: The Universal Prefix Argument. * Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix. @end menu @end macro @node Introduction @chapter Introduction Introduction Text @chapter CTitle @section First Section @Gela-Menu @subsection First SubSection @section Second Section @Gela-Menu Regards Christopher
@point{} Gntting a Star in Texinfo.
The manual says that
The @point{} command is displayed as ‘∗’, either a pointed star or (when that is not available) the ASCII sequence ‘-!-’.
I am getting ‘-!-’. How can I fix this so that I get ‘∗’ a pointed star?
Regards
C*
Re: @point{} Gntting a Star in Texinfo.
Correct. Thank You Gavin
Regards
C*
Sent: Friday, October 16, 2020 at 3:54 PM
From: "Gavin Smith"
To: "Christopher Dimech"
Cc: "help-texinfo gnu"
Subject: Re: @point{} Gntting a Star in Texinfo.
On Fri, Oct 16, 2020 at 03:31:27PM +0200, Christopher Dimech wrote:
> The manual says that
>
>
>
> The @point{} command is displayed as , either a pointed star or (when that is not available) the ASCII sequence -!-.
>
>
>
> I am getting -!-. How can I fix this so that I get a pointed star?
>
>
>
> Regards
>
> C*
>
If this is for the Info output I think you need to have
@documentencoding UTF-8
in the file.
Re: @point{} Gntting a Star in Texinfo.
Where do you customarily put the command? In the header part?
@c %**start of header
@setfilename gungadin-elisp-abbrev.info
@documentencoding UTF-8
@set Volume-1
@set Gela-Version 1.0
@set Emacs-Version 27.0
@set Date October 21, 2020.
@c %**end of header
Sent: Friday, October 16, 2020 at 3:54 PM
From: "Gavin Smith"
To: "Christopher Dimech"
Cc: "help-texinfo gnu"
Subject: Re: @point{} Gntting a Star in Texinfo.
On Fri, Oct 16, 2020 at 03:31:27PM +0200, Christopher Dimech wrote:
> The manual says that
>
>
>
> The @point{} command is displayed as
> , either a pointed star or (when that is
> not available) the ASCII sequence -!-.
>
>
>
> I am getting -!-. How can I fix this so that
> I get a pointed star?
>
>
>
> Regards
>
> C*
>
If this is for the Info output I think you need to have
@documentencoding UTF-8
in the file.
@ref displays "see" strings in info files
I am writing a manual using makeinfo
I have written the following
@macro Gela-Menu
@paragraphindent 0
@* * @ref{Modifier-Keys}:: Modifier Keys on Lisp Machine Keyboards.
@* * @ref{Key-Mnemonics}:: Mnemonics that identify specific keys.
@paragraphindent 3
@end macro
This was to add a Menu at the end of sections, so that users can continue
using the manual without having to go to the top of the buffer.
But I have noticed that the output is as follows even though @ref is not
supposed
so generate the "see" string when loading the info file.
* see Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards.
* see Key-Mnemonics:: Mnemonics that identify specific keys.
This also happens when @ref is not put in a @macro. And same "see" effect when
put in @table as well.
Regards
C*
Re: @ref displays "see" strings in info files
Apologies, Gavin,
Fine. Still, the problem should not occur. Is it a problem with Texinfo or
Emacs?
What could fix the problem? Have read the comment but does not provide clear
details. To me anyway.
Regards
Christopher
Sent: Friday, October 16, 2020 at 9:35 PM
From: "Gavin Smith"
To: "Christopher Dimech"
Cc: "help-texinfo gnu"
Subject: Re: @ref displays "see" strings in info files
On Fri, Oct 16, 2020 at 06:06:23PM +0200, Christopher Dimech wrote:
> I am writing a manual using makeinfo
>
> I have written the following
>
> @macro Gela-Menu
> @paragraphindent 0
> @* * @ref{Modifier-Keys}:: Modifier Keys on Lisp Machine Keyboards.
> @* * @ref{Key-Mnemonics}:: Mnemonics that identify specific keys.
> @paragraphindent 3
> @end macro
>
> This was to add a Menu at the end of sections, so that users can continue
> using the manual without having to go to the top of the buffer.
>
> But I have noticed that the output is as follows even though @ref is not
> supposed
> so generate the "see" string when loading the info file.
>
> * see Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards.
> * see Key-Mnemonics:: Mnemonics that identify specific keys.
>
> This also happens when @ref is not put in a @macro. And same "see" effect when
> put in @table as well.
>
> Regards
> C*
This has been asked so many times that I've written a whole new FAQ about
it, to which I refer you ;-)
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=35f4537b19697a448d4aa36389e6f1f736905281
Re: @ref displays "see" strings in info files
It does not make a difference what value you put (t, nil, other). One either
gets "see"
or *note.
You don't see any problem with texinfo right, but a problem with Emacs. Correct?
Regards
C*
Sent: Friday, October 16, 2020 at 9:54 PM
From: "Gavin Smith"
To: "Christopher Dimech"
Cc: "help-texinfo gnu"
Subject: Re: @ref displays "see" strings in info files
You could check the Emacs documentation of Info-hide-note-references.
https://www.gnu.org/software/emacs/manual/html_node/info/Emacs-Info-Variables.html
On Fri, Oct 16, 2020 at 8:52 PM Christopher Dimech wrote:
>
>
> Hi, Gavin,
>
> Fine. Still, the problem should not occur. Is it a problem with Texinfo or
> Emacs?
> What could fix the problem? Have read the comment but does not provide clear
> details. To me anyway.
>
> Regards
> Christopher
>
> Sent: Friday, October 16, 2020 at 9:35 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @ref displays "see" strings in info files
> On Fri, Oct 16, 2020 at 06:06:23PM +0200, Christopher Dimech wrote:
> > I am writing a manual using makeinfo
> >
> > I have written the following
> >
> > @macro Gela-Menu
> > @paragraphindent 0
> > @* * @ref{Modifier-Keys}:: Modifier Keys on Lisp Machine Keyboards.
> > @* * @ref{Key-Mnemonics}:: Mnemonics that identify specific keys.
> > @paragraphindent 3
> > @end macro
> >
> > This was to add a Menu at the end of sections, so that users can continue
> > using the manual without having to go to the top of the buffer.
> >
> > But I have noticed that the output is as follows even though @ref is not
> > supposed
> > so generate the "see" string when loading the info file.
> >
> > * see Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards.
> > * see Key-Mnemonics:: Mnemonics that identify specific keys.
> >
> > This also happens when @ref is not put in a @macro. And same "see" effect
> > when
> > put in @table as well.
> >
> > Regards
> > C*
>
> This has been asked so many times that I've written a whole new FAQ about
> it, to which I refer you ;-)
>
> https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=35f4537b19697a448d4aa36389e6f1f736905281[https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=35f4537b19697a448d4aa36389e6f1f736905281]
Re: @ref displays "see" strings in info files
Hi, Gavin,
Fine. Still, the problem should not occur. Is it a problem with Texinfo or Emacs?
What could fix the problem? Have read the comment but does not provide clear
details. To me anyway.
Regards
Christopher
Sent: Friday, October 16, 2020 at 9:35 PM
From: "Gavin Smith"
To: "Christopher Dimech"
Cc: "help-texinfo gnu"
Subject: Re: @ref displays "see" strings in info files
On Fri, Oct 16, 2020 at 06:06:23PM +0200, Christopher Dimech wrote:
> I am writing a manual using makeinfo
>
> I have written the following
>
> @macro Gela-Menu
> @paragraphindent 0
> @* * @ref{Modifier-Keys}:: Modifier Keys on Lisp Machine Keyboards.
> @* * @ref{Key-Mnemonics}:: Mnemonics that identify specific keys.
> @paragraphindent 3
> @end macro
>
> This was to add a Menu at the end of sections, so that users can continue
> using the manual without having to go to the top of the buffer.
>
> But I have noticed that the output is as follows even though @ref is not supposed
> so generate the "see" string when loading the info file.
>
> * see Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards.
> * see Key-Mnemonics:: Mnemonics that identify specific keys.
>
> This also happens when @ref is not put in a @macro. And same "see" effect when
> put in @table as well.
>
> Regards
> C*
This has been asked so many times that I've written a whole new FAQ about
it, to which I refer you ;-)
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=35f4537b19697a448d4aa36389e6f1f736905281
Re: @ref displays "see" strings in info files
Have sent an bug-report to the Emacs group. Keep awesome. Regards Christopher - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Friday, October 16, 2020 at 10:23 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @ref displays "see" strings in info files > > On Fri, Oct 16, 2020 at 10:18:55PM +0200, Christopher Dimech wrote: > > > > > > > > It does not make a difference what value you put (t, nil, other). One > > either gets "see" > > or *note. > > > > You don't see any problem with texinfo right, but a problem with Emacs. > > Correct? > > > > Yes. >
Re: @ref displays "see" strings in info files
The solution is to use this declaration in Emacs Init files for info. (setq Info-hide-note-references 'hide) "hide" is not in the Manual, but shows up when doing "M-x describe-variable Info-hide-note-references" Shall update the documentation. Would be worthwhile to add a few words about this alto in the Texinfo Manual. There could be a section: "Viewing Info Files in Emacs", with some details. I could write something. > Sent: Friday, October 16, 2020 at 10:23 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @ref displays "see" strings in info files > > On Fri, Oct 16, 2020 at 10:18:55PM +0200, Christopher Dimech wrote: > > > > > > > > It does not make a difference what value you put (t, nil, other). One > > either gets "see" > > or *note. > > > > You don't see any problem with texinfo right, but a problem with Emacs. > > Correct? > > > > Yes. >
Conconformity between Menu and sectioning
I am writing an texinfo manual file, and makeinfo to giving the
following two warnings even if what is in the menu and the sectioning
is correct.
./01-gela-intro.texi:831: warning: node `Cmd-ArgDescr' is next for
`Intactv-Function' in menu but not in sectioning
./01-gela-intro.texi:856: warning: node `Intactv-Function' is prev for
`Cmd-ArgDescr' in menu but not in sectioning
In the file I have
> @c ==
> @ignore
> * [Intactv-Function] Interactive Functions
> ___ _ _ ___
> |_ _|_ _| |_ __ _ __| |___ __ | __| _ __
> | || ' \ _/ _` / _| _\ V / | _| ' \/ _|
> |___|_||_\__\__,_\__|\__|\_/ |_||_||_\__|
>
> @end ignore
>
> @node Intactv-Function
> @section Interactive Function
>
> Interactive functions can be called from Emacs by the user via "M-x" or
> via a keybinding. An Elisp function becomes an interactive command when
> its body contains the interactive declaration.
>
> (interactive Arg-Descriptor)
>
> The interactive declaration allows users to pass arguments to a User
> Defined Function. Passing parameters to functions can be done via (1)
> the Universal Prefix Argument, or (2) from a Mini-Buffer Prompt that
> displays a message to help the user input the command argument.
>
> When the Arg-Descriptor is not used, no arguments are used when calling
> the command. Thusly, no arguments are passed to the interactive
> command.
>
> @c --
> @ignore
> ** [Cmd-ArgDescr] Interactive options for Arg-Descriptor
> @end ignore
>
> @node Cmd-ArgDescr
> @subsection Interactive options for Arg-Descriptor
>
> @noindent There are three possibilities for the Interactive Argument
> Descriptor:
>
> @c No item marks displayed with @w{}
> @itemize @w{}
>@item -String-
>@* @ @ @ Code Letters used to interpret parameter.
>
>@item -Emacs Lisp Expression-
>@* @ @ @ Evaluates to a list of the actual arguments.
>
>@item -Argument Omitted, or set to 'nil'-
>@* @ @ @ Function will not take parameter arguments.
> @end itemize
>
>
> @c --
> @ignore
> ** [Numrv-CodeLtr] Interactive String Arg-Descriptor for Numeric Values
> @end ignore
>
> @node Numrv-CodeLtr
> @subsection Interactive String Arg-Descriptor for Numeric Values
>
> When the Interactive Arg-Descriptor is a String, Code Letters are used
> to define the argument and how the argument is passed. For numeric
> values, the Code Letters 'N', 'p', and 'n' are frequently used. When
> using the Code Letter 'N', the numeric value can be passed in two ways.
> When using the Mini-Buffer Prompt, a message is appended after the Code
> Letter. The message appears in the Mini-Buffer to help the user input
> the argument for the command he wants executed.
>
> @multitable @columnfractions 0.01 0.05 0.95
> @item @tab "N" @tab
> Uses Mini-Buffer Prompt or Universal Prefix.
>
> @item @tab "p" @tab
> Utilises Universal Prefix converted to number. Does not use Prompt.
> @* @* @ @ @ C-u Arg M-x Command-Name
>
> @item @tab "n" @tab
> Uses Mini-Buffer Prompt. Not designed to use Prefix.
> @* @* @ @ @ M-x Command-Name Arg
> @end multitable
@menu for Subsections and Anchors
Dear Compeers, Noticed that makeinfo gets confused when I use subsections and want to include the node in the .info file. makeinfo also seems confused if in the menu I put a reference which is an anchor. Regards Christopher
Displaying Sections of Code in Monospace
Dear Compeers, Is there a construct to display sections of code in texinfo that continue across many lines. Have been using @format. But I have noticed that the characters are not monospace. Regards Christopher
@menu puts too many restrictions to produce the .info file
I wish to point out that @menu puts a lot of restrictions on running makeinfo. 1. Having an unreferenced node 2. lacking some item in the Menu 3. Not having same order in menu as in Sectioning 4. Menu complains about @anchor 5. Menu complains of @sebsectioning I do get use cases where the menu is there to help the user towards a particular direction. However when I produce documentation in Pdf I want it too look are an ordered manual. There are many reasons why a person would want a menu that differs from the sectioning. - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: Anchors do not work with makeinfo
I have sent you a small test, it is not with anchors with with simple nodes and sections: I am getting the following output from makeinfo makeinfo 00-gungadin-elisp-abbrev.texi; emacs gungadin-elisp-abbrev.info 00-gungadin-elisp-abbrev.texi:22: warning: @end ifclear should only appear at a line beginning 00-gungadin-elisp-abbrev.texi:55: warning: @end ifset should only appear at a line beginning ./gela-test.texi:49: warning: node next `Intactv-Function' in menu `Tpsw-Cmd' and in sectioning `Specif-Intactv-Arg' differ ./gela-test.texi:79: warning: unreferenced node `Specif-Intactv-Arg' ./gela-test.texi:79: warning: node `Numrv-CodeLtr' is next for `Specif-Intactv-Arg' in sectioning but not in menu ./gela-test.texi:79: warning: node `Intactv-Function' is prev for `Specif-Intactv-Arg' in sectioning but not in menu ./gela-test.texi:79: warning: node `Introduction' is up for `Specif-Intactv-Arg' in sectioning but not in menu ./gela-test.texi:9: node `Introduction' lacks menu item for `Specif-Intactv-Arg' despite being its Up target ./gela-test.texi:120: warning: unreferenced node `Numrv-CodeLtr' ./gela-test.texi:120: warning: node `Tpsw-Cmd' is next for `Numrv-CodeLtr' in sectioning but not in menu ./gela-test.texi:120: warning: node `Specif-Intactv-Arg' is prev for `Numrv-CodeLtr' in sectioning but not in menu ./gela-test.texi:120: warning: node `Introduction' is up for `Numrv-CodeLtr' in sectioning but not in menu ./gela-test.texi:9: node `Introduction' lacks menu item for `Numrv-CodeLtr' despite being its Up target ./gela-test.texi:153: warning: node `Fwd-Jumps' is next for `Tpsw-Cmd' in sectioning but not in menu ./gela-test.texi:153: warning: node prev `Tpsw-Cmd' in menu `Intactv-Function' and in sectioning `Numrv-CodeLtr' differ ./gela-test.texi:205: warning: unreferenced node `Fwd-Jumps' ./gela-test.texi:205: warning: node `Bck-Jumps' is next for `Fwd-Jumps' in sectioning but not in menu ./gela-test.texi:205: warning: node `Tpsw-Cmd' is prev for `Fwd-Jumps' in sectioning but not in menu ./gela-test.texi:205: warning: node `Introduction' is up for `Fwd-Jumps' in sectioning but not in menu ./gela-test.texi:9: node `Introduction' lacks menu item for `Fwd-Jumps' despite being its Up target ./gela-test.texi:255: warning: unreferenced node `Bck-Jumps' ./gela-test.texi:255: warning: node `Fwd-Jumps' is prev for `Bck-Jumps' in sectioning but not in menu ./gela-test.texi:255: warning: node `Introduction' is up for `Bck-Jumps' in sectioning but not in menu ./gela-test.texi:9: node `Introduction' lacks menu item for `Bck-Jumps' despite being its Up target Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "topmenu-gtk-module" > Sent: Tuesday, October 20, 2020 at 2:41 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Anchors do not work with makeinfo > > On Tue, Oct 20, 2020 at 02:35:25PM +0200, Christopher Dimech wrote: > > When I use an anchor, the link does not work when I use @ref > > when I run makeinfo > > You'll need to be much more specific. Which format? What does not > work? makeinfo by itself setup links but does not use them. Also > probably the texinfo code, reasonably trimmed down to the interesting > elements may be needed. > > -- > Pat > 00-gungadin-elisp-abbrev.texi Description: TeXInfo document gela-test.texi Description: TeXInfo document
Re: @menu puts too many restrictions to produce the .info file
It should not be assumed that the author made mistakes. At least not problems with how one structures the document. Because when using texi2pdf all of that is acceptable. Message is intended to start a discussion on improving some aspects for those intending to do non-trivial work in texinfo. And start tackling some of them. Let's start with a useful case. Let's forget about subsections for now. Test 1: Suppose I change the last @node to @anchor. Makeinfo will complain that menu and sections are not in order. If you try to mouse click on the menu at the location of the @anchor, the Anchor Reference will not work. - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Tuesday, October 20, 2020 at 3:03 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @menu puts too many restrictions to produce the .info file > > On Tue, Oct 20, 2020 at 02:49:28PM +0200, Christopher Dimech wrote: > > I wish to point out that @menu puts a lot of restrictions on running > > makeinfo. > > > > > > Do you have a use case in which this would not be an error: > > 1. Having an unreferenced node > > 2. lacking some item in the Menu > > 3. Not having same order in menu as in Sectioning > > This one seems to me to be ok, @node and @anchor should be unique, it is > an intended feature: > > 4. Menu complains about @anchor > > 5. Menu complains of @sebsectioning > > > > I do get use cases where the menu is there to help the user > > towards a particular direction. However when I produce > > documentation in Pdf I want it too look are an ordered manual. > > > > There are many reasons why a person would want a menu that differs > > from the sectioning. > > I agree with you on 2, 3, and 5. In general those warnings are ok, as > these are likely to be mistakes, but I agree that the user may want > menus structures to be different from the tree structure and suppress > the corresponding warnings somewhat selectively. @novalidate > and --no-validate could be of use in that case, but it may also be too > broad. > > One possibility could be to add a customization variable, like > ALLOW_NON_TREE_NODE_STRUCTURE > > -- > Pat >
Anchors do not work with makeinfo
When I use an anchor, the link does not work when I use @ref when I run makeinfo
Re: @menu puts too many restrictions to produce the .info file
Sure, but ALLOW_NON_TREE_NODE_STRUCTURE is not there. > Sent: Tuesday, October 20, 2020 at 4:15 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @menu puts too many restrictions to produce the .info file > > On Tue, Oct 20, 2020 at 04:10:41PM +0200, Christopher Dimech wrote: > > Where are the customization variables documented? > > In the node 'Customization Variables' of the texinfo manual > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Customization-Variables.html > > -- > Pat >
Re: Setting Page Size and displaying result correctly
These are two considerations for Page Sizes as described below. 1. Consistency in applying commands It is true that the manual says that @pagesizes refers to text-area. However, it should be remembered that papersizes such as @afourpaper and @afivepaper always refer to the actual size of the paper. The default margins will then set the text-area. The manual already says that setting of margins is considered an elaboration that should customarily be defined using commands in texinfo.tex. Just as @afourpaper and @afivepaper always refer to to actual page size rather than text-area, other settings for page sizes should ideally follow same rule - User sets the actual page size, and not the size of the text area. 2. Possibilities for using Texinfo for Screencasts, especially screencasts that include the display of mathematical expressions. The difficulty setting a different page size does not crop up for software manuals. But the problem crops up when you want to use a texinfo document for a screen cast. In such an instance, changing the page size would be important, because the standard paper sizes make the text too small for display purposes on the screen. This would enable texinfo to be used in many other circumstances in addition to simply writing manuals. Regards Christopher > Sent: Tuesday, October 06, 2020 at 6:11 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Setting Page Size and displaying result correctly > > On Tue, Oct 06, 2020 at 09:58:32AM +0200, Christopher Dimech wrote: > > Dear Compeers, > > > > I have recently mentioned allowing multiline titles in structured commands > > (e.g. @chapter, @section, @unnumberedsec) > > > > Another Texinfo aspect to mention is properly setting the page size using > > @pagesizes. > > > > Firstly, if one uses a smaller pagesize, the resulting pdf simply cuts the > > page out to the required size. This means that the part of the text, > > figures, > > etc ... that is outside the area are cut out. > > That does not appear to be strictly true, as formatting with a narrow > page width does shorten the formatted lines, only that the right-hand > margin completely disappears. > > > Have used @pagesizes 250mm,176mm I have also noticed that the result is > > almost > > correct, showing a pagesize of 250mm,182mm. Perhaps it is also something to > > look > > at. > > Note the following excerpt from the manual: > > >>> > Examples: > > @pagesizes 200mm,150mm > and > @pagesizes 11.5in > >This would be reasonable for printing on B5-size paper. To > emphasize, this command specifies the size of the _text area_, not the > size of the paper (which is 250mm by 177mm for B5, 14in by 8.5in for > legal). > >>> > > So the page size that appears in e.g. a PDF reader would not match > the arguments exactly. > > > > > Making @pagesizes work would be extremely beneficial for users. > > I doubt that many people will actually print Texinfo manuals onto paper, > but I don't see why it couldn't be fixed for other paper sizes (assuming > someone works out how to do it). Are you going to print on paper that is > 250x176 mm? Is that B5? >
Macro introduces \par in Table of Contents
I have written the macro uSubSec
However I have found that a \par is introduced in the Table of Contents
when the title continues on the next line. How can this problem be solved?
Example:
@uSubSec{@value{SecLb}, Probabilistic Characterisation of
Microseismicity}
@macro uSubSec{label, titl}
@set lb \label\
@ifclear USubSec--No--Label
@unnumberedsubsec @value{lb} @ \titl\
@end ifclear
@ifset USubSec--No--Label
@unnumberedsubsec \titl\
@end ifset
@end macro
Re: Macro introduces \par in Table of Contents
I have also implemented the following macro
@macro InlRmk{a}
@ifset Margi
@b{\a\}
@end ifset
@end macro
And I was able to call the macro with multiline information, including
commas (no need to use @comma{}) and everything is being written
@InlRmk{@bullet{} [1] This Work - Waveforms from Sicilian Stations [2]
Hidden Signals - Revealed by Hilbert, Stockwell & Wavelet Tfm [3]
Improve Subsurface Estimn - Irregular Distribution of Earthqk, Low
Tectonic Movements.}
> Sent: Saturday, October 03, 2020 at 12:18 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Macro introduces \par in Table of Contents
>
> On Sat, Oct 3, 2020 at 9:20 AM Christopher Dimech wrote:
> >
> >
> > I have written the macro uSubSec
> >
> > However I have found that a \par is introduced in the Table of Contents
> > when the title continues on the next line. How can this problem be solved?
> >
> > Example:
> >
> > @uSubSec{@value{SecLb}, Probabilistic Characterisation of
> > Microseismicity}
> >
> > @macro uSubSec{label, titl}
> >
> > @set lb \label\
> > @ifclear USubSec--No--Label
> > @unnumberedsubsec @value{lb} @ \titl\
> > @end ifclear
> >
> > @ifset USubSec--No--Label
> > @unnumberedsubsec \titl\
> > @end ifset
> >
> > @end macro
>
> Your input does not work with texi2any either, although in that case
> the part of the argument on the next line is not even included in the
> argument to @unnumberedsubsec. Hence, I do not think that this should
> be made to work with TeX.
>
> The best solution I've come up with is to use DEL as a comment
> character. (I've never seen a use for this before!)
>
> \input texinfo
>
> @macro uSubSec{label, titl}
>
> @set lb \label\
> @unnumberedsubsec @value{lb} @ \titl\
>
> @end macro
>
>
> @uSubSec{@value{SecLb}, Probabilistic ^?
> Characterisation of Microseismicity}
>
>
> where ^? is the DEL character (byte value 0x7f). This appears to work
> perfectly with both texinfo.tex and texi2any.
>
> I found that starting a new line, like
>
> @uSubSec{@value{SecLb},
> Probabilistic Characterisation of Microseismicity}
>
> worked with texi2any, but not with TeX.
>
> As usual with macro handling in Texinfo, this is not easy to fix, and
> any fix risks breaking something else. There is an @xeatspaces macro
> being used around macro arguments that is not being expanded until
> quite late on, which might be better expanded earlier with a given
> value of active newline, but it would be very complicated if not
> impossible to expand this earlier without fully expanding the macro
> arguments at the same time (probably some complex arrangement of
> \expandafter's which would differ depending on the number of macro
> arguments, or repeatedly reading the argument text as a macro argument
> and moving expanded arguments one by one to the end). Even if it's
> possible it's probably better not to try as it would be error-prone
> and hard to understand after the fact.
>
> Another option was changing the definition of active newline away from
> @par to a space or an empty string, but this broke using a macro
> inside an environment like @example.
>
Re: Macro introduces \par in Table of Contents
I have now tried
@uSubSec{@value{SecLb}, Probabilistic Characterisation of^?
Microseismicity}
But this is giving me the following output in my pdf file.
As seen, the ^? is being printed
B Probabilistic Characterisation of^?
Microseismicity
And the Table of Contents is showing
B Probabilistic Characterisation of^?\par Microseismicity . . . . . . . . 5
> Sent: Saturday, October 03, 2020 at 12:18 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Macro introduces \par in Table of Contents
>
> On Sat, Oct 3, 2020 at 9:20 AM Christopher Dimech wrote:
> >
> >
> > I have written the macro uSubSec
> >
> > However I have found that a \par is introduced in the Table of Contents
> > when the title continues on the next line. How can this problem be solved?
> >
> > Example:
> >
> > @uSubSec{@value{SecLb}, Probabilistic Characterisation of
> > Microseismicity}
> >
> > @macro uSubSec{label, titl}
> >
> > @set lb \label\
> > @ifclear USubSec--No--Label
> > @unnumberedsubsec @value{lb} @ \titl\
> > @end ifclear
> >
> > @ifset USubSec--No--Label
> > @unnumberedsubsec \titl\
> > @end ifset
> >
> > @end macro
>
> Your input does not work with texi2any either, although in that case
> the part of the argument on the next line is not even included in the
> argument to @unnumberedsubsec. Hence, I do not think that this should
> be made to work with TeX.
>
> The best solution I've come up with is to use DEL as a comment
> character. (I've never seen a use for this before!)
>
> \input texinfo
>
> @macro uSubSec{label, titl}
>
> @set lb \label\
> @unnumberedsubsec @value{lb} @ \titl\
>
> @end macro
>
>
> @uSubSec{@value{SecLb}, Probabilistic ^?
> Characterisation of Microseismicity}
>
>
> where ^? is the DEL character (byte value 0x7f). This appears to work
> perfectly with both texinfo.tex and texi2any.
>
> I found that starting a new line, like
>
> @uSubSec{@value{SecLb},
> Probabilistic Characterisation of Microseismicity}
>
> worked with texi2any, but not with TeX.
>
> As usual with macro handling in Texinfo, this is not easy to fix, and
> any fix risks breaking something else. There is an @xeatspaces macro
> being used around macro arguments that is not being expanded until
> quite late on, which might be better expanded earlier with a given
> value of active newline, but it would be very complicated if not
> impossible to expand this earlier without fully expanding the macro
> arguments at the same time (probably some complex arrangement of
> \expandafter's which would differ depending on the number of macro
> arguments, or repeatedly reading the argument text as a macro argument
> and moving expanded arguments one by one to the end). Even if it's
> possible it's probably better not to try as it would be error-prone
> and hard to understand after the fact.
>
> Another option was changing the definition of active newline away from
> @par to a space or an empty string, but this broke using a macro
> inside an environment like @example.
>
Re: Macro introduces \par in Table of Contents
With the following code it worked
@uSubSec{@value{SecLb}, Probabilistic Characterisation of@
Microseismicity}
But you are saying that it code breaks using a macro
inside an environment like @example.
However, relating to sections and subsections, @uSubSec
won't be called in side an example.
Can one do multiline titles using @unnumberedsec?
Does the multiline thing fail when using macros, or is the problem
only related to defining sections?
> Sent: Saturday, October 03, 2020 at 12:18 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Macro introduces \par in Table of Contents
>
> On Sat, Oct 3, 2020 at 9:20 AM Christopher Dimech wrote:
> >
> >
> > I have written the macro uSubSec
> >
> > However I have found that a \par is introduced in the Table of Contents
> > when the title continues on the next line. How can this problem be solved?
> >
> > Example:
> >
> > @uSubSec{@value{SecLb}, Probabilistic Characterisation of
> > Microseismicity}
> >
> > @macro uSubSec{label, titl}
> >
> > @set lb \label\
> > @ifclear USubSec--No--Label
> > @unnumberedsubsec @value{lb} @ \titl\
> > @end ifclear
> >
> > @ifset USubSec--No--Label
> > @unnumberedsubsec \titl\
> > @end ifset
> >
> > @end macro
>
> Your input does not work with texi2any either, although in that case
> the part of the argument on the next line is not even included in the
> argument to @unnumberedsubsec. Hence, I do not think that this should
> be made to work with TeX.
>
> The best solution I've come up with is to use DEL as a comment
> character. (I've never seen a use for this before!)
>
> \input texinfo
>
> @macro uSubSec{label, titl}
>
> @set lb \label\
> @unnumberedsubsec @value{lb} @ \titl\
>
> @end macro
>
>
> @uSubSec{@value{SecLb}, Probabilistic ^?
> Characterisation of Microseismicity}
>
>
> where ^? is the DEL character (byte value 0x7f). This appears to work
> perfectly with both texinfo.tex and texi2any.
>
> I found that starting a new line, like
>
> @uSubSec{@value{SecLb},
> Probabilistic Characterisation of Microseismicity}
>
> worked with texi2any, but not with TeX.
>
> As usual with macro handling in Texinfo, this is not easy to fix, and
> any fix risks breaking something else. There is an @xeatspaces macro
> being used around macro arguments that is not being expanded until
> quite late on, which might be better expanded earlier with a given
> value of active newline, but it would be very complicated if not
> impossible to expand this earlier without fully expanding the macro
> arguments at the same time (probably some complex arrangement of
> \expandafter's which would differ depending on the number of macro
> arguments, or repeatedly reading the argument text as a macro argument
> and moving expanded arguments one by one to the end). Even if it's
> possible it's probably better not to try as it would be error-prone
> and hard to understand after the fact.
>
> Another option was changing the definition of active newline away from
> @par to a space or an empty string, but this broke using a macro
> inside an environment like @example.
>
Re: Macro introduces \par in Table of Contents
Have done some more tests and the \par problem extends also to multiline
titles for @chapter, @section, @subsection, and @subsubsec.
For users, using @ at the end of each line is acceptable. It also gets
the correct title alignments. Using DEL character is not a good strategy
for users.
@chapter{Amplitude Asymmetry in the Empirical Green Function Amplitude@
Asymmetry}
@section{Strong amplitude asymmetries between the Retarded Causal Branch@
and the Advanced Anti-Causal contribution to the Coherence Function}
Allowing Multiline titles would be a good improvement to Texinfo, especially
for users to write on complicated topics, books, etc.
One possible solution could include the addition of a Title Construction
Function one can call, which would allow multiline titles to be properly
passed to sections and subsections, including the unnumbered versions.
I have previously constructed macros with several arguments. My experience has
been that parameter values are being passed correctly even if they continue for
several lines. Might need to write some small examples and send them, to see
that works and what does not.
Regards
Christopher
> Sent: Saturday, October 03, 2020 at 6:02 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Macro introduces \par in Table of Contents
>
> On Sat, Oct 3, 2020 at 2:32 PM Christopher Dimech wrote:
> >
> >
> > With the following code it worked
> >
> > @uSubSec{@value{SecLb}, Probabilistic Characterisation of@
> > Microseismicity}
>
> Yes, that would look like it would work, as there is a single letter
> control sequence "@NL" where NL is a newline character (see info node
> "(texinfo)Multiple Spaces").
>
> > But you are saying that it code breaks using a macro
> > inside an environment like @example.
> >
> > However, relating to sections and subsections, @uSubSec
> > won't be called in side an example.
>
> Yes, but other macros may be.
>
> > Can one do multiline titles using @unnumberedsec?
>
> This is not supported and if it works, it works by accident.
>
> > Does the multiline thing fail when using macros, or is the problem
> > only related to defining sections?
>
> It is because the @unnumberedsec command takes its argument on a single line.
>
Using @chapter but starting from an arbitrary number, 6 say.
I am using @chapter in a document. The chapters start with the numerical value of 1. Is there a possibility to start the chapters from another number, e.e., from chapter 6.
Using Macros
I have been scrutinising the Texinfo files for the book "Free Software Free
Society"
where he defines some macros in texinfo.tex
In the code file not-ipr.texi there is the command
@chapter Did You Say ``Intellectual
Property''?@entrybreak{}It's@tie{}a@tie{}Seductive@tie{}Mirage
I do not think that @entrybreak{} is a standard texinfo command when checking
the manual.
In the file texinfo.tex I have found defined
\def\entrybreak{\hfil\break}%
I want to do a similar thing in one of my documents that uses @part because the
part
title is bit long and I would like to break it along multiple lines.
Because I keep to 72 columns in the code, I want to split the long part titles,
but have noticed that texinfo takes only the entry on the same line as @part.
@alias ebr = entrybreak
@set ta @ebr{}New Ideas in Seismic
@set tb @ebr{}Observatory Practice
@part PART I @*@*@* @value{ta}@*@value{tb}
@part PART I @*@*@* @value{ta}@*@value{tb}
Using @alias on unnumberedsec
I have noticed that trying to use alias on @unnumberedsec makes texinfo behave strangely when trying to get the manual. @alias usec = unnumberedsec - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Texinfo in Org-Mode without changing syntax highlighting
I am writing a document in texinfo, but I also have some commands in Org-Mode so that if I change my Emacs Major Mode to Org-Mode I get an easy way to traverse my texinfo code. However I would like to keep the syntax highlighting as the use set for texinfo, rather than that of org-mode. I share a way to do that? - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: @menu puts too many restrictions to produce the .info file
Understood. Had thought it exists but not documented, but reading your comment again, you are correct. Would one be able to call it inside the source code? Finding a variable like that becomes vital for those which plan deviates from the popular way. I also mention that Makeinfo states that @ifset and @ifclear should only appear at a line beginning. I suggest that it be made as other region commands that are allowed indentation. Regards Christopher - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Tuesday, October 20, 2020 at 4:45 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @menu puts too many restrictions to produce the .info file > > On Tue, Oct 20, 2020 at 04:33:53PM +0200, Christopher Dimech wrote: > > Sure, but ALLOW_NON_TREE_NODE_STRUCTURE is not there. > > Of course, this is something to be added that I proposed in the mail > following your report. It is not implemented already! I would prefer > to have Gavin look at the proposal before implmenting that (and not > before the week end if I do it). > > > > > > > > > > Sent: Tuesday, October 20, 2020 at 4:15 PM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "help-texinfo gnu" > > > Subject: Re: @menu puts too many restrictions to produce the .info file > > > > > > On Tue, Oct 20, 2020 at 04:10:41PM +0200, Christopher Dimech wrote: > > > > Where are the customization variables documented? > > > > > > In the node 'Customization Variables' of the texinfo manual > > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Customization-Variables.html > > > > > > -- > > > Pat > > > >
Re: @menu puts too many restrictions to produce the .info file
I attach a file to see how I used floats to display images where indenting makes sense as in standard languages. Things are fine with sectioning, title, ... and can use whole line. But I see many instances when users want to include many @if* statements, including within other constructs. I see that conditional expressions can become very important for large works. > Sent: Tuesday, October 20, 2020 at 5:59 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" , "help-texinfo gnu" > > Subject: Re: @menu puts too many restrictions to produce the .info file > > On Tue, Oct 20, 2020 at 05:30:15PM +0200, Christopher Dimech wrote: > > I also mention that Makeinfo states that @ifset and @ifclear > > should only appear at a line beginning. I suggest that it be made > > as other region commands that are allowed indentation. > > This is not necessarily easy to implement and it would be very easy > for you to move the commands to the beginnings of their lines. It's > never been encouraged to indent whole-line commands in Texinfo. > Ch03b--Chmed--Igm.texi Description: TeXInfo document
@smallverbatim
Have been playing with @quotation, @example, @display, @format, @verbatim and their small versions and found them all useful, particularly the small versions. However, a small version of @verbatim is not present. It would help to also have @smallverbatim. Regards Christopher
Re: @ref without page numbers
I could not follow it very well.
My problem occurs in pdf output. How is the page number important, is there
notion
of page number in other formats, not just only on pdf? How are links and page
numbers
related? Can one do anything for the pdf case only?
> Sent: Friday, October 23, 2020 at 8:42 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @ref without page numbers
>
> On Fri, Oct 23, 2020 at 03:42:11PM +0200, Christopher Dimech wrote:
> >
> > Although it is useful to have @ref followed by page numbers, page
> > numbers can make the text very difficult to follow when there there
> > are two or more references cluttered together, or when the same
> > reference is used (particularly when this happens on the same page).
> >
> > Are there ways to stop @ref from showing page numbers?
> >
> > Although the most important command is @ref, the same thing applies
> > to other reference commands (@xref, @pref).
> >
> > Regards
> > Christopher
>
> I wrote about this in the manual recently:
>
> https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=35f4537b19697a448d4aa36389e6f1f736905281
>
> +@item Yes, but how do I get a plain link, with no extra markup?
> +
> +You can't. Info is a plain text format that is displayed mostly as-is
> +in the viewers, and without the @samp{*note} text there would be nothing
> +to mark text as a link. Additionally, in printed output there is no
> +such thing as a plain link, as the page number of the target would have
> +to be printed somewhere.
> +
> +If you really want a plain link in HTML output without affecting other
> +output formats, you could create a macro with conditional definitions for
> +each output format.
>
Re: @ref without page numbers
I agree with your evaluation Patrice. > Sent: Saturday, October 24, 2020 at 1:56 AM > From: "Patrice Dumas" > To: "Karl Berry" > Cc: dim...@gmx.com, help-texinfo@gnu.org > Subject: Re: @ref without page numbers > > On Fri, Oct 23, 2020 at 04:41:30PM -0600, Karl Berry wrote: > > Christopher, if you want to write full technical documents with lots of > > references, math, etc., why don't you just use LaTeX? Texinfo is not > > designed for this. Trying to shoehorn it to fit seems fraught with problems. > > LaTeX is not very practical to write program documentation. Texinfo is > not so good at math and bibliography. However, when you need both, for > instance when you write a manual for a program dealing with mathematics, > I find Texinfo with tex4ht or latex2html and now mathjax to be better > compromise than LaTeX as LaTeX is very poor for program documentation. > The html obtained, for instance is much more suitable when going through > Texinfo. > > -- > Pat >
Re: @ref without page numbers
Dear Gavin,
You are quite right, if the manual is printed, one needs the page numbers.
I would be satisfied with an option in which the page number is printed
as a superscript @sup{page-no} (similar to footnote numbers) next to the
closing square bracket.
That is, from this
Section 1.13 [Intactv-Function], page 11,
to this
Section 1.13 [Intactv-Function]@sup{11},
The would solve the problem, yet keep requirements intact.
Regards
Christopher
> Sent: Friday, October 23, 2020 at 10:05 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @ref without page numbers
>
> On Fri, Oct 23, 2020 at 09:18:12PM +0200, Christopher Dimech wrote:
> > I could not follow it very well.
> >
> > My problem occurs in pdf output. How is the page number important, is
> > there notion
> > of page number in other formats, not just only on pdf? How are links and
> > page numbers
> > related? Can one do anything for the pdf case only?
>
> If the manual is printed on paper, the page number is needed for the
> reader to look up the cross-reference.
>
> This issue has been discussed in the past:
>
> https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00029.html
> https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00036.html
>
> (BTW the discussion containing that message goes into a lot of other
> extraneous matters - please try and keep discussion germane to the
> issue at hand.)
>
>
Re: @ref without page numbers
There might be no precedent, yet I have found a use case to highlight
the point in one of my mathematical documents.
Look at this
[Schimmel & Gallart (2007)], page 29, [Bensen, Ritzwoller et al. (2007)],
page 27, [Ventosa et al. (2017)], page 30,
and compare with this
[Schimmel & Gallart (2007)]^p29, [Bensen, Ritzwoller et al. (2007)]^p27,
[Ventosa et al. (2017)]^p30,
We can use @sup{pN} to remove the longer (full) page representation.
I had passed the document around and the full output was deemed problematic.
The problem not only occurs with printed but also with pdf. And as you pointed
out the page number is required if the document is printed, and we can also
solve
the readability problem that occurs with multiple @ref next to each other.
Was not aware that you tackled the task of removing the page number completely.
But, I am unsure how I can introduce your modification in my file to test it.
Nevertheless, my alternative brief page numbering would resolve the readability
problem pointed out to me.
Regards
Christopher
> Sent: Friday, October 23, 2020 at 11:44 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @ref without page numbers
>
> On Fri, Oct 23, 2020 at 10:40:52PM +0200, Christopher Dimech wrote:
> > Dear Gavin,
> >
> > You are quite right, if the manual is printed, one needs the page numbers.
> >
> > I would be satisfied with an option in which the page number is printed
> > as a superscript @sup{page-no} (similar to footnote numbers) next to the
> > closing square bracket.
> >
> > That is, from this
> >
> > Section 1.13 [Intactv-Function], page 11,
> >
> > to this
> >
> > Section 1.13 [Intactv-Function]@sup{11},
> >
> > The would solve the problem, yet keep requirements intact.
> >
> > Regards
> > Christopher
>
> There's no precedent for this - this looks like a footnote reference.
> Would it not be simpler to miss out the page number, as in my patch
> here?
>
> https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00048.html
>
Re: @ref without page numbers
Pdf are very important in business settings, and because Texinfo allows inclusion of mathematical expression (through @math, @tex), the pdf output is very useful. Regards Christopher > Sent: Friday, October 23, 2020 at 10:05 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @ref without page numbers > > On Fri, Oct 23, 2020 at 09:18:12PM +0200, Christopher Dimech wrote: > > I could not follow it very well. > > > > My problem occurs in pdf output. How is the page number important, is > > there notion > > of page number in other formats, not just only on pdf? How are links and > > page numbers > > related? Can one do anything for the pdf case only? > > If the manual is printed on paper, the page number is needed for the > reader to look up the cross-reference. > > This issue has been discussed in the past: > > https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00029.html > https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00036.html > > (BTW the discussion containing that message goes into a lot of other > extraneous matters - please try and keep discussion germane to the > issue at hand.) > >
Re: @ref without page numbers
Because my package requires them. I managed to get a decent bibliography good enough for release. If some humps are smoothed, I can see that texinfo would have great capability. For instance, having math in html produced much interest. Gavin has also got to some small page sizes as well, which makes texinfo very attractive. Stallman has written his book in texinfo. I also found it much better than you envisage. Regards Christopher - Christopher Dimech Chief Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Saturday, October 24, 2020 at 12:41 AM > From: "Karl Berry" > To: dim...@gmx.com > Cc: gavinsmith0...@gmail.com, help-texinfo@gnu.org > Subject: Re: @ref without page numbers > > Christopher, if you want to write full technical documents with lots of > references, math, etc., why don't you just use LaTeX? Texinfo is not > designed for this. Trying to shoehorn it to fit seems fraught with problems. > > Using @ref for bibliography entries seems like a problem in the first > place. Texinfo doesn't have any real bibliography support. All the > workarounds in the world are not going to produce robust output or > processing. > > Just my unasked-for $.002, sorry, > Karl >
Re: @smallverbatim
Was not a request for consistency. I find the @small versions more useful
because the customary one makes the text too big. For instance, a quotation
is much better when using @smallquotation.
I needed to use verbatim as it does not expand commands, but needed the
small version.
> Sent: Saturday, October 24, 2020 at 12:41 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @smallverbatim
>
> On Fri, Oct 23, 2020 at 02:37:01PM +0200, Christopher Dimech wrote:
> > Have been playing with @quotation, @example, @display, @format, @verbatim
> > and their small versions and found them all useful, particularly the small
> > versions.
> >
> > However, a small version of @verbatim is not present. It would help to also
> > have @smallverbatim.
>
> It could be done (although somebody would have to do the work for it). In
> my opinion, however, the @small... variants should never have been invented,
> and consistency is not a great argument for adding more commands.
>
> My preferred solution would be to use @small... variants unconditionally
> for certain page sizes.
>
> I know it is not very flexible, but texinfo.tex has never been very
> flexible.
>
> For example, for B6:
>
> diff --git a/doc/texinfo.tex b/doc/texinfo.tex
> index 6c5754f3d..fb9b69d58 100644
> --- a/doc/texinfo.tex
> +++ b/doc/texinfo.tex
> @@ -7663,13 +7663,13 @@ might help (with 'rm \jobname.?? \jobname.??s')%
>% without the active space; thus we have to use \xdef and \gobble.
>% The \egroup ends the \verbbox started at the end of the last line in
>% the block.
> \endgroup
> %
> \envdef\verbatim{%
> -\setupverbatim\doverbatim
> +\setnormaldispenv\setupverbatim\doverbatim
> }
> \let\Everbatim = \afterenvbreak
>
>
> % @verbatiminclude FILE - insert text of file in verbatim environment.
> %
> @@ -11489,12 +11489,13 @@ directory should work if nowhere else does.}
> \def\bsixpaper{{\globaldefs = 1
>\afourpaper
>\internalpagesizes{140mm}{100mm}%
> {-6.35mm}{-12.7mm}%
> {\bindingoffset}{14pt}%
> {176mm}{125mm}%
> + \let\SETdispenvsize=\smallword
>\globaldefs = 0
> }}
>
>
> % @pagesizes TEXTHEIGHT[,TEXTWIDTH]
>
>
Re: @smallverbatim
Gavin, so what's left is to have @verbatim accept \smallword? > Sent: Saturday, October 24, 2020 at 2:17 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @smallverbatim > > On Sat, Oct 24, 2020 at 01:33:36PM +0200, Christopher Dimech wrote: > > Was not a request for consistency. I find the @small versions more useful > > because the customary one makes the text too big. For instance, a quotation > > is much better when using @smallquotation. > > > > I needed to use verbatim as it does not expand commands, but needed the > > small version. > > The latest version works quite well with @bsixpaper, IMHO, because > small fonts are on by default for @verbatim, @example, etc. and > the margin is reduced, so most existing uses of it are OK without > overlong lines. > > https://ftp.gnu.org/gnu/texinfo/texinfo.tex >
Re: @smallverbatim
Yes, I confirm they are good and approve them being set by dafault. Do you mean I simply call @quotation rather than @smallquotation. It certainly makes things easier. Almost always I use @smallbook, and even for @smallbook, the small versions are also better. Can you see if they can be used by default as well for @smallbook. > Sent: Saturday, October 24, 2020 at 2:17 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @smallverbatim > > On Sat, Oct 24, 2020 at 01:33:36PM +0200, Christopher Dimech wrote: > > Was not a request for consistency. I find the @small versions more useful > > because the customary one makes the text too big. For instance, a quotation > > is much better when using @smallquotation. > > > > I needed to use verbatim as it does not expand commands, but needed the > > small version. > > The latest version works quite well with @bsixpaper, IMHO, because > small fonts are on by default for @verbatim, @example, etc. and > the margin is reduced, so most existing uses of it are OK without > overlong lines. > > https://ftp.gnu.org/gnu/texinfo/texinfo.tex >
Re: @ref without page numbers
Dear Gavin,
Have now tested your modification of texinfo.tex to remove the page
number and if works.
I also put the page number as a superscript. It is easy to do, and
independently of whether customary or not, it does solve particular
problems if you could be so kind to put the options to do them.
With the appended 'p', it should not conflict with footnotes.
Furthermore as seen in the subscript commands 1. and 2., because the
page number it after close right bracket ']' and before the comma ','
of the reference, people would not confuse it with a footnote. Appending
the letter 'p' could act as abbreviation if people think it is really
necessary.
1. Like this
\turnoffactive \sup{\refx{#1-pg}{}}%
2. and like this
\turnoffactive \sup{p\refx{#1-pg}{}}%
%\ifoutputpagenumberinxref
% But we always want a comma and a space:
%,\space
%
% output the `page 3'.
%\turnoffactive \putwordpage\tie\sup\refx{#1-pg}{}%
\turnoffactive \sup{p\refx{#1-pg}{}}%
% Add a , if xref followed by a space
\if\space\noexpand\tokenafterxref ,%
\else\ifx\ \tokenafterxref ,% @TAB
\else\ifx\*\tokenafterxref ,% @*
\else\ifx\ \tokenafterxref ,% @SPACE
\else\ifx\ \tokenafterxref ,%@NL
\else\ifx\tie\tokenafterxref ,% @tie
\fi\fi\fi\fi\fi\fi
%\fi
-
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Friday, October 23, 2020 at 11:44 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @ref without page numbers
>
> On Fri, Oct 23, 2020 at 10:40:52PM +0200, Christopher Dimech wrote:
> > Dear Gavin,
> >
> > You are quite right, if the manual is printed, one needs the page numbers.
> >
> > I would be satisfied with an option in which the page number is printed
> > as a superscript @sup{page-no} (similar to footnote numbers) next to the
> > closing square bracket.
> >
> > That is, from this
> >
> > Section 1.13 [Intactv-Function], page 11,
> >
> > to this
> >
> > Section 1.13 [Intactv-Function]@sup{11},
> >
> > The would solve the problem, yet keep requirements intact.
> >
> > Regards
> > Christopher
>
> There's no precedent for this - this looks like a footnote reference.
> Would it not be simpler to miss out the page number, as in my patch
> here?
>
> https://lists.gnu.org/archive/html/bug-texinfo/2016-11/msg00048.html
>
Different behaviour when using @macro with @sp, @vskip, @noindent
I have the following texinfo code. But if I put the same commands
in @macro, I see more vertical space when displaying the example
when calling the @macro Tuni.
@macro Tuni{sp,sk}
@iftex
@sp \sp\
@vskip \sk\
@end iftex
@noindent
@end macro
---file---
Key Shortcuts are grouped into units called Key Input
Events.
@c @Tuni{0,2mm}
@iftex
@sp 0
@vskip 2mm
@end iftex
@noindent
@example
(global-set-key (kbd "C-t ") #'IntchgStc-Prev)
@end example
file---
Re: @smallverbatim
> This would be a good idea if not for the fact that there > are already documents using @smallbook and they may use > an inconsistent mix of @smallexample and @example etc. One solution could be to have @smallbook set @example, etc. with a small size anyway. A warning can be added in the texinfo for people to remove calls to the @small versions and eventually remove their use after a year or so. I tend to find Warnings useful as I can go change my commands at the time I am modifying the files and running the texinfo programs. c* > Sent: Saturday, October 24, 2020 at 2:58 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @smallverbatim > > On Sat, Oct 24, 2020 at 02:30:33PM +0200, Christopher Dimech wrote: > > Yes, I confirm they are good and approve them being set > > by dafault. Do you mean I simply call @quotation > > rather than @smallquotation. It certainly makes things > > easier. Almost always I use @smallbook, and even for > > @smallbook, the small versions are also better. Can > > you see if they can be used by default as well for > > @smallbook. > > This would be a good idea if not for the fact that there > are already documents using @smallbook and they may use > an inconsistent mix of @smallexample and @example etc. > One thing you could do is add an extra line to your source > file, like: > > @smallbook > @set dispenvsize small > > Then you would not have to bother with writing @smallexample, etc. > > > > >
Re: @smallverbatim
You are correct, it works. Missed the \setnormaldispenv in \envdef\verbatim. > Sent: Saturday, October 24, 2020 at 3:31 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @smallverbatim > > On Sat, Oct 24, 2020 at 03:16:44PM +0200, Christopher Dimech wrote: > > Have tried '@set dispenvsize small' for @quotation, @example, @display, > > @format. > > > > However, @verbatim is still using a large font. > > > > Did you update to the most recent texinfo.tex? Looks ok to me. > > \input texinfo > > normal > @set dispenvsize small > > @verbatim > a a > bb d > f ff > llm dsalk alke > @end verbatim > > normal > > @example > a a > bb d > f ff > llm dsalk alke > @end example > > @bye > >
Re: @smallverbatim
Have tried '@set dispenvsize small' for @quotation, @example, @display, @format. However, @verbatim is still using a large font. > Sent: Saturday, October 24, 2020 at 2:58 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @smallverbatim > > On Sat, Oct 24, 2020 at 02:30:33PM +0200, Christopher Dimech wrote: > > Yes, I confirm they are good and approve them being set > > by dafault. Do you mean I simply call @quotation > > rather than @smallquotation. It certainly makes things > > easier. Almost always I use @smallbook, and even for > > @smallbook, the small versions are also better. Can > > you see if they can be used by default as well for > > @smallbook. > > This would be a good idea if not for the fact that there > are already documents using @smallbook and they may use > an inconsistent mix of @smallexample and @example etc. > One thing you could do is add an extra line to your source > file, like: > > @smallbook > @set dispenvsize small > > Then you would not have to bother with writing @smallexample, etc. > > > > >
Vertical Spacing less than @sp 1
Is it possible to introduce a spacing between two lines of text to be less than '@sp 1' or '@*', perhaps by half. When I am writing a list or enumeration using @* look as too much of a vertical space. @enumerate ---@item -Line Text 1 -@item -Line Text 2 @sp 0.5 ---@item -Line Text 3 @end enumerate
Macro Determining of Arguments
I have written a macro for texinfo
@macro GPage{titl, titlCn, subTitl, subTitlCn, date}
...
@end macro
Call to macro
@GPage{, 1 @ User Freedom, Sub, Test, Friday 24 July 2020}
Is there a way to determine whether an argument has been passed or not?
Currently I am checking using set variables
@macro GPage{titl, titlCn, subTitl, subTitlCn, date}
@title @sc{\titl\ @* \titlCn\}
@inlineifset{GSt, @subtitle \subTitl\}
@inlineifset{GToday , @subtitle \subTitlCn\ @today{}}
@inlineifclear{GToday , @subtitle \subTitlCn\ \date\}
@end macro
-
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
Re: Macro Determining of Arguments
I use @set
Example:
@titlepage
@set GSt
@GPage{titl, titlCn, subTitl, subTitlCn, date}
@end titlepage
-
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Saturday, July 25, 2020 at 8:06 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Macro Determining of Arguments
>
> On Sat, Jul 25, 2020 at 08:03:58PM +0200, Christopher Dimech wrote:
> >
> > I have written a macro for texinfo
> >
> > @macro GPage{titl, titlCn, subTitl, subTitlCn, date}
> > ...
> > @end macro
> >
> >
> > Call to macro
> > @GPage{, 1 @ User Freedom, Sub, Test, Friday 24 July 2020}
> >
> > Is there a way to determine whether an argument has been passed or not?
> > Currently I am checking using set variables
> >
> > @macro GPage{titl, titlCn, subTitl, subTitlCn, date}
> >
> > @title @sc{\titl\ @* \titlCn\}
> > @inlineifset{GSt, @subtitle \subTitl\}
> > @inlineifset{GToday , @subtitle \subTitlCn\ @today{}}
> > @inlineifclear{GToday , @subtitle \subTitlCn\ \date\}
> >
> > @end macro
>
> I don't see how your macro works. How are GSt etc. set?
>
> I don't think there is a good way to do this. You are better off using
> several macros with different parameters, and not having any empty
> arguments. Another option is not using macros at all.
>
>
Removing page from @ref{}
I need to remove the page number that is displayed when calling
@ref{Node--Item,, Item}.
Is this possible to do if outputting pdf.
Unicode char @u8: not defined for Texinfo
Am getting the following text when using texi2pdf. I cannot understand exactly what is producing the problem.the problem Unicode char @u8: not defined for Texinfo --- Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7 @texttt Copyright:[]| (3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] l.1142: Unicode char @u8: not defined for Texinfo l.1143: Unicode char @u8: not defined for Texinfo l.1143: Unicode char @u8: not defined for Texinfo [12] l.1189: Unicode char @u8: not defined for Texinfo l.1189: Unicode char @u8: not defined for Texinfo l.1190: Unicode char @u8: not defined for Texinfo l.1195: Unicode char @u8: not defined for Texinfo l.1195: Unicode char @u8: not defined for Texinfo l.1203: Unicode char @u8: not defined for Texinfo l.1203: Unicode char @u8: not defined for Texinfo [13] l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1213: Unicode char @u8: not defined for Texinfo l.1218: Unicode char @u8: not defined for Texinfo [14] (./03c-chmed-rfc.texi [15] [16] [17]) [18] (CC By-Nc-Nd 4) (/home/hagbard/01cuneus/freelic/latest/freelic-3.4/cc/by-nc-nd/by-nc-nd.texi [19] [20] - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Comment lines inside a @macro
Is it problematic including comment lines inside a macro? @macro showAllChmedIgm @c Station Locations (Sicily and Circum-Ambient Region) @c Label: igc03-sicl-circumambrg [1] @igmSiclCircumambrg @end macro
float identifier has been already used
I made the following macro to display an image. I am encountering a problem
because when I want to display the image image a second time, the same float
identifier (name{igc03-sicl-circumambrg}) has been already used.
@macro igmSiclCircumambrg
@set fignm igc03-sicl-circumambrg [01]
@float Figure,igc03-sicl-circumambrg
@center @image{@value{igc03-path}/igc03-01-sicl-circumambrg,12cm,,,.png}
@paragraphindent 0
@caption{@strong{Sites of the 102 seismic stations in Sicily and in
its Circum-Ambient Regions for use in the microseismic analysis
effort.}}
@shortcaption{Sites of the 102 seismic stations in Sicily and in its
Circum-Ambient Regions for use in the microseismic analysis effort.}
@end float
@end macro
@image and fifth argument during html output
Gavin,
Can one use for html output the command that follows. It was not working
even when the file exists. Texinfo was not giving an error, however, the
image was not being displayed in html when using .png.
@image{file.w.h.alttext,.png}
Regards
Christopher
Re: Displaying images for html output
> Sent: Sunday, November 22, 2020 at 12:46 AM > From: "Patrice Dumas" > To: "Gavin Smith" > Cc: "Christopher Dimech" , "help-texinfo gnu" > > Subject: Re: Displaying images for html output > > On Sat, Nov 21, 2020 at 05:20:00PM +, Gavin Smith wrote: > > On Thu, Nov 19, 2020 at 10:11 PM Patrice Dumas wrote: > > > I think that if the path does not starts with . or .. or is an absolute > > > path, it would make sense > > > 1) to search in include directories (I think that the current directory > > > is always in front of of the search path) > > > 2) to check if the directories and image file exist in the destination > > > directory and if not copy the file > > > > > > For point 2), there could be a customization variable to prevent the > > > copy, that would be off in the default case, but can be turned on for > > > the users who want backward compatibility or do something else by > > > themselves, for instance use links. > > > > That sounds okay, as searching include directories matches what > > happens with TeX. When you say "current directory" this should mean > > the directory containing the Texinfo file, not the working directory > > from which texi2any is run. (What to do when a file in a subdirectory > > is @include'd and then references an image, I don't know.) I got to handle that situation an a daily basis. What I have found is that the include file that references the image got to have a number of Level Variables, so the texinfo can still get to the image. I can share a copy of the code so texinfo can get to the next level for complicated projects. Shall we do it? I have been pushing texinfo to the limit and the code would certainly provide ideas so that texinfo could handle those instances adequately. Regards Christopher > I think that it is the current directory, not the directory containing > the Texinfo file, but I do not think that it matters much. I think that > the point is to copy the image file from where it is found to the > destination directory. > > -- > Pat >
@image with @value using texi2pdf
Running the following command using texi2pdf gives errors.
Output is correct for html output.
- Command -
@set imgf ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg
@image{@value{imgf}.png}
- Errors -
(3 @ Microseismic Analysis of the Central Mediterranean Region) [-2]
(./03bCh--Chmed--Igm.texi)
./03aCh--Chmed--html.texi:316: TeX capacity exceeded, sorry [input stack size=5
000].
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
...
l.316 @image{@value{imgf}.png}
./03aCh--Chmed--html.texi:316: ==> Fatal error occurred, no output PDF file pr
oduced!
Transcript written on 03aCh--Chmed--html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Re: @image and fifth argument during html output
Apologies, have changed to dvorak keyboard and hit period instead. I used it for
parameter illustration.
The command does not display as expected for html output. The output is
produced
with no errors, but the image is not displayed, displaying alttext instead.
When the file exists, using .png does not find the file.
@image{file,8cm,13cm,alttext,.png}
Regards
Christopher
> Sent: Wednesday, November 25, 2020 at 6:15 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @image and fifth argument during html output
>
> On Wed, Nov 25, 2020 at 05:31:49PM +0100, Christopher Dimech wrote:
> >
> > Gavin,
> >
> > Can one use for html output the command that follows. It was not working
> > even when the file exists. Texinfo was not giving an error, however, the
> > image was not being displayed in html when using .png.
> >
> > @image{file.w.h.alttext,.png}
> >
> > Regards
> > Christopher
>
> This looks wrong as the arguments should be separated by commas, not
> periods:
>
> > @image{file.w.h.alttext,.png}
> > @image{file,w,h,alttext,.png}
>
> Also w and h have to be numbers.
>
>
Re: Width and Height in @image for Html Output fail
> Sent: Wednesday, November 25, 2020 at 7:07 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Width and Height in @image for Html Output fail
>
> On Thu, Nov 19, 2020 at 07:51:30PM +0100, Christopher Dimech wrote:
> > It occurs to me that one requires two image versions:
> > (1) An image for high-resolution pdf; and (2) Another
> > image for low resolution image html.
> >
> > Can we think of only having one command that calls
> > @image, rather than two (i.e. rather than having @iftex
> > and @ifhtml)?
> >
> > For instance,
> >
> > @image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png}
> >
> > For pdf output will use the file
> > ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.png
> >
> > For html output will use
> > ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.html.png
> >
> > Or the like.
>
> If we could make @value work properly in the first argument of @image,
> then this could be used to configure image resolution. So you
> would do
>
> @image{../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.@value{imageres}.png}
>
> and elsewhere do
>
> @set imageres high
>
> to look for a file
>
> ../Ideogr/Ch03b--Chmed/igc03--01--Sicl--CircAmRg.high.png
>
> I will look at the @value issue.
Yes, allowing @value would allow various possibilites and likely solve
other things, as you have mentioned.
Kind Regards
Christopher
Re: Latest Development Version - @image with @value
Using the following does not work for me. Do I require some setup? Have
also got the latest texinfo.tex
@set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
@image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
@image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
First call to @image works, the second fails.
> Sent: Thursday, December 03, 2020 at 6:41 PM
> From: "Christopher Dimech"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @macro line continuation
>
> It looks like I installed correctly though
>
> hagbard@fuckup:
> + ~
> which texi2pdf
> /usr/local/bin/texi2pdf
>
> hagbard@fuckup:
> + ~
> ls -lrt /usr/local/bin/texi2pdf
> -rwxr-xr-x 1 root root 1246 Dec 3 07:52 /usr/local/bin/texi2pdf
>
>
> -
> Christopher Dimech
> General Administrator - Naiad Informatics - GNU Project (Geocomputation)
> - Geophysical Simulation
> - Geological Subsurface Mapping
> - Disaster Preparedness and Mitigation
> - Natural Resource Exploration and Production
> - Free Software Advocacy
>
>
> > Sent: Thursday, December 03, 2020 at 6:28 PM
> > From: "Christopher Dimech"
> > To: "help-texinfo gnu"
> > Subject: Latest Development Version - @macro line continuation
> >
> > I have installed the latest development version but seeing an error.
> >
> > Perhaps I did not install it properly?
> >
> > --- Source Code
> >
> > @macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
> >
> > @title @sc{\titl\ @* \titlCn\}
> > @subtitle \subtitl\
> > @subtitle \subtitlCn\
> >
> > @center @strong{Text}
> > @center Text
> > @center \date\
> > @author Christopher Dimech
> > @iftex
> > @page
> > @insertcopying
> > @end iftex
> >
> > @end macro
> >
> > @TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
> > Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > Errors ---
> >
> > texi2pdf 03aCh-Chmed-html.texi
> > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
> > (preloaded format=pdfetex)
> > restricted \write18 enabled.
> > entering extended mode
> >
> > (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
> > Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
> > page headings, tables, conditionals, indexing, sectioning, toc,
> > environments,
> > defuns, macros, cross references, insertions,
> > (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> > This is `epsf.tex' v2.7.4 <14 February 2011>
> > ) localization, formatting, and turning on texinfo input format.)
> > (../LibMacro/DocuSeg.mc.texi)
> > Runaway argument?
> > {
> > ./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
> >
> >@par
> > ^^M
> > Chapter 3 Tuesday September 15@comma {} 2020
> > @eatspaces ...@expandafter @trim@ @expandafter {#1
> >}
> > ... Tuesday September 15@comma {} 2020}
> > @unskip @hfil
> > @centersub ...enalty @fi @line {@kern @leftskip #1
> > @kern @rightskip }
> > @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> > @let @centersub @relax
> > ...
> > l.119 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > ./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
> > @centersub ...@kern @leftskip #1@kern @rightskip }
> >
> > @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> > @let @centersub @relax
> > l.25 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > @scanmacro ...@eatspaces }@scantokens {#1@comment}
> >
> > l.119 Chapter 3 Tuesday September 15@comma{} 2020}
> >
> > [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
> > (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
> > Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
> > @texttt Copyright:[]|
> >
> > Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
> > @texttt Copyright:
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 5:45 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > Using the following does not work for me. Do I require some setup? Have
> > also got the latest texinfo.tex
> >
> > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> >
> > First call to @image works, the second fails.
>
> Well, I tried @image with @value with an absolute directory
> name, and it worked. What output are you getting from TeX? Are you
> sure the latest texinfo.tex is being read?
Let me check again. Any hints on how to know which one is being used?
texi2pdf 03aCh-Chmed-html.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
./03aCh-Chmed-html.texi:121: TeX capacity exceeded, sorry [input stack size=500
0].
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
...
l.121 ...pter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:121: ==> Fatal error occurred, no output PDF file prod
uced!
Transcript written on 03aCh-Chmed-html.log.
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
./03aCh-Chmed-html.texi:121: TeX capacity exceeded, sorry [input stack size=500
0].
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
@makevalueexpandable ->@let @value
= @expandablevalue @catcode `@-=@other @c...
@value ->@begingroup @makevalueexpandable
@valuexxx
...
l.121 ...pter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:121: ==> Fatal error occurred, no output PDF file prod
uced!
Transcript written on 03aCh-Chmed-html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Latest Development Version - @macro line continuation
I have installed the latest development version but seeing an error.
Perhaps I did not install it properly?
--- Source Code
@macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
@title @sc{\titl\ @* \titlCn\}
@subtitle \subtitl\
@subtitle \subtitlCn\
@center @strong{Text}
@center Text
@center \date\
@author Christopher Dimech
@iftex
@page
@insertcopying
@end iftex
@end macro
@TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
Chapter 3 Tuesday September 15@comma{} 2020}
Errors ---
texi2pdf 03aCh-Chmed-html.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(../LibMacro/DocuSeg.mc.texi)
Runaway argument?
{
./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
@par
^^M
Chapter 3 Tuesday September 15@comma {} 2020
@eatspaces ...@expandafter @trim@ @expandafter {#1
}
... Tuesday September 15@comma {} 2020}
@unskip @hfil
@centersub ...enalty @fi @line {@kern @leftskip #1
@kern @rightskip }
@\center ...{@hfil @ignorespaces #1@unskip @hfil }
@let @centersub @relax
...
l.119 Chapter 3 Tuesday September 15@comma{} 2020}
./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
@centersub ...@kern @leftskip #1@kern @rightskip }
@\center ...{@hfil @ignorespaces #1@unskip @hfil }
@let @centersub @relax
l.25 Chapter 3 Tuesday September 15@comma{} 2020}
@scanmacro ...@eatspaces }@scantokens {#1@comment}
l.119 Chapter 3 Tuesday September 15@comma{} 2020}
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
(/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
@texttt Copyright:[]|
Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
@texttt Copyright:[]|
(3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] )
(see the transcript file for additional information)pdfTeX warning (dest): name
{ii} has been referenced but does not exist, replaced by a fixed one
Output written on 03aCh-Chmed-html.pdf (5 pages, 95768 bytes).
Transcript written on 03aCh-Chmed-html.log.
/usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
Re: Latest Development Version - @macro line continuation
It looks like I installed correctly though
hagbard@fuckup:
+ ~
which texi2pdf
/usr/local/bin/texi2pdf
hagbard@fuckup:
+ ~
ls -lrt /usr/local/bin/texi2pdf
-rwxr-xr-x 1 root root 1246 Dec 3 07:52 /usr/local/bin/texi2pdf
-
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Thursday, December 03, 2020 at 6:28 PM
> From: "Christopher Dimech"
> To: "help-texinfo gnu"
> Subject: Latest Development Version - @macro line continuation
>
> I have installed the latest development version but seeing an error.
>
> Perhaps I did not install it properly?
>
> --- Source Code
>
> @macro TdrPage{titl, titlCn, subtitl, subtitlCn, date}
>
> @title @sc{\titl\ @* \titlCn\}
> @subtitle \subtitl\
> @subtitle \subtitlCn\
>
> @center @strong{Text}
> @center Text
> @center \date\
> @author Christopher Dimech
> @iftex
> @page
> @insertcopying
> @end iftex
>
> @end macro
>
> @TdrPage{Microseismic Analysis of the, Central Mediterranean Region,,,
> Chapter 3 Tuesday September 15@comma{} 2020}
>
> Errors ---
>
> texi2pdf 03aCh-Chmed-html.texi
> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex
> Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions,
> (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.)
> (../LibMacro/DocuSeg.mc.texi)
> Runaway argument?
> {
> ./03aCh-Chmed-html.texi:119: Paragraph ended before @trim@ was complete.
>
>@par
> ^^M
> Chapter 3 Tuesday September 15@comma {} 2020
> @eatspaces ...@expandafter @trim@ @expandafter {#1
>}
> ... Tuesday September 15@comma {} 2020}
> @unskip @hfil
> @centersub ...enalty @fi @line {@kern @leftskip #1
> @kern @rightskip }
> @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> @let @centersub @relax
> ...
> l.119 Chapter 3 Tuesday September 15@comma{} 2020}
>
> ./03aCh-Chmed-html.texi:119: Extra }, or forgotten @endgroup.
> @centersub ...@kern @leftskip #1@kern @rightskip }
>
> @\center ...{@hfil @ignorespaces #1@unskip @hfil }
> @let @centersub @relax
> l.25 Chapter 3 Tuesday September 15@comma{} 2020}
>
> @scanmacro ...@eatspaces }@scantokens {#1@comment}
>
> l.119 Chapter 3 Tuesday September 15@comma{} 2020}
>
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) [-1]
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc)
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.toc) (History)
> (/home/hagbard/01cuneus/tdr/03ch/03aCh-Chmed-html.aux)
> Overfull \hbox (4.44653pt too wide) in paragraph at lines 8--8
> @texttt Copyright:[]|
>
> Overfull \hbox (4.44653pt too wide) in paragraph at lines 7--7
> @texttt Copyright:[]|
> (3 @ Microseismic Analysis of the Central Mediterranean Region) [-2] [1] )
> (see the transcript file for additional information)pdfTeX warning (dest):
> name
> {ii} has been referenced but does not exist, replaced by a fixed one
>
> hare/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmbx12.pfb> exlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmcsc10.pfb> e/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi10.pfb> f-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb> /fonts/type1/public/amsfonts/cm/cmr10.pfb> type1/public/amsfonts/cm/cmsl10.pfb> public/amsfonts/cm/cmtt10.pfb>
> Output written on 03aCh-Chmed-html.pdf (5 pages, 95768 bytes).
> Transcript written on 03aCh-Chmed-html.log.
> /usr/local/bin/texi2dvi: pdfetex exited with bad status, quitting.
>
>
>
>
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 8:06 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Sat, Dec 05, 2020 at 03:31:19AM +0100, Christopher Dimech wrote:
> > I often end up with may @ifset and @ifclear in my documents.
> > Is it acceptable to call the following command? It does work
> > as expected.
> >
> > @inlineifset{igrank-1, @set imgpth /home/hagbard}
> >
> > imgpth: @value{imgpth}
>
> Yes, that looks fine. You could also do
>
> @ifset igrank-1
> @set imgpth /home/hagbard
> @end ifset
Wonderful. Was using @ifset but at times using @inlineifset
is more convenient, whilst keeping initialisations compact.
This is most useful when setting up images (e.g. for the pdf
and html, where two files could be used).
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 8:03 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 11:20:47PM +0100, Christopher Dimech wrote: > > Understood. It would be extremely helpful to users trying to test or check > > the development version to put a remark about /doc/texinfo.tex in the > > section > > "Getting a Copy of the Git Repository". > > I think it is clear if you say to a user, "that issue is fixed in > the development version in git", then they should know to look in git, > not on the website for versions released for users. I understand the scheme now, but is far from obvious to me. You could simplify the following page, with a short categorisation and description of the whole working scheme https://www.gnu.org/software/texinfo/ start === TEXINFO === Texinfo is the official documentation format of the GNU project. It is used by many non-GNU projects as well. Texinfo uses a single source file to produce output in a number of formats, both online and printed (DVI, HTML, Info, PDF, XML, etc.). This means that instead of writing different documents for online information and another for a printed manual, you need write only one document. And when the work is revised, you need revise only that one document. The Texinfo system is well-integrated with GNU Emacs. Official Releases = Download the latest official version (also on all GNU mirrors). Older releases are also available. Get the latest version of the texinfo.tex macro file. The macro file updates the latest official release before the next full Texinfo release is made. The file is used for converting Texinfo source to DVI or PDF files for printing and viewing, using the TeX typesetting system. Because the file is updated much more frequently; ) please use the latest version. The Development Version === You can browse and get a copy of the Development Version of Texinfo using the Git Repository. The latest development version of the texinfo.tex macro file can be found in the directory "doc" of the Texinfo development source tree. Texinfo Manual and Reference Card = The Texinfo manual and standalone Info reader manual from the latest official release, in various formats. See the GNU documentation page for manuals for other GNU packages. The Texinfo reference card formatted for letter-size paper (four landscape pages) and for A4-size paper. Texinfo Project === Texinfo project page The NEWS file listing notable changes by release, the ChangeLog file detailing all changes, and the TODO file with future projects large and small, awaiting volunteers. Pretests If available, the latest pretest. Pretests are inherently unstable. Please try them and report problems—that's why they are done, so the official release will be as reliable as it can be. === MAILING LISTS ... etc ===
Re: Latest Development Version - @image with @value
> Sent: Saturday, December 05, 2020 at 12:30 AM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 11:43:09PM +0100, Christopher Dimech wrote: > > Fantastic. Things age working now. texinfo.tex is mentioned in the README > > file. > > > > There are three files README, INSTALL, INSTALL.generic. When reading them, > > they continue > > referring around between themselves. > > The INSTALL.generic is "out of our control" it is the generic > INSTALL file for autoconf/automake based packages. So we add > a specific INSTALL file for the texinfo specifics in link with > installing. > > > Can there be just one README (otherwise have just one INSTALL file) with > > abbreviated > > set of instructions of typical installation, at the beginning? > > I am not that convinced that it is a good idea. The reference to > INSTALL appears at the beginning of the README and I think that INSTALL* > are best separate as otherwise the INSTALL specific parts would get in the > way of having a short README. As I said above, the INSTALL.generic is > outside of our control, which makes the only real option merging the > specific INSTALL in the README. > > > Thank you both for bearing with me. But it was not so clear and quick > > about what exactly one should do when trying development versions. > > It is indeed not clear nor quick. So we agree > It seems to me that README-hacking contains most of the information > (though not about building in a different directory from the source), > and then the INSTALL file. It is a bit scattered, but the problem is > that different persons will not need the same information depending on > where they come from and need to do (from a release, the developpment > source, testing or installing). Also the overall build system is not > simple, there is an intrinsic complexity that we can't really remove by > instructions (the whole autoconf/automake/gettext, with two translated > sets, and additionally some Makefile parts being generated). And README-hacking. Fuckin hell!!! And then, it does not contain all the necessary information. > It is not so clear to me what/if we need to add more information, people > testing from the development tree are very few, answering to questions > by mail could be more efficient than trying to document everything. I could have got on your nerves, because everything was good on your side. > That being said, if you have specific ideas of changes to the files, do > not hesitate to propose, in particular in the form of patches. Perhaps a document describing what you have said to me (in some text file). There were similar problems with Gcc in the past, which were eventually sorted out. Used to test some very dodgy versions as new standards were being implemented. I am in the process of releasing the Gunga Din Software, that is focused on setting a Gnu System for new users of Gnu-Like. Will include abbreviated versions of Gnu User Guide and Gnu Admin Guide. Could write something there. But have got to spend some time getting my head around how it would look like, and that the description works for those who need to understand what to do so they can get back rapidly to their own work - that's my focus. You could go through it and decide on whether to include some parts. Regards Christopher > > > > In general there is also a need to run > ./autogen.sh > in the source thee before going into the build directory. Yes, that's what I had to do. We can write some of these scenarios vith typical examples. > > > > % mkdir build > > % cd build > > % srcdir/configure [options] [target] > > % make > > % make install > > % cp srcdir/doc/texinfo.tex workdir > > > > Where workdir is the directory of your main Texinfo input file. > > > > ---- > > > > > > > Sent: Friday, December 04, 2020 at 10:53 PM > > > From: "Patrice Dumas" > > > To: "Christopher Dimech" > > > Cc: "Gavin Smith" , "help-texinfo gnu" > > > > > > Subject: Re: Latest Development Version - @image with @value > > > > > > On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote: > > > > > Sent: Friday, December 04, 2020 at 10:30 PM > > > > > From: "Patrice Dumas" > > > > > To: "Christopher Dimech" > > > > > Cc: "Gavin Smith" , "help-texinfo gnu" > > > > > > > > > > Subject: Re: Latest Development Version
Re: Latest Development Version - @image with @value
I often end up with may @ifset and @ifclear in my documents.
Is it acceptable to call the following command? It does work
as expected.
@inlineifset{igrank-1, @set imgpth /home/hagbard}
imgpth: @value{imgpth}
> Sent: Saturday, December 05, 2020 at 12:30 AM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 11:43:09PM +0100, Christopher Dimech wrote:
> > Fantastic. Things age working now. texinfo.tex is mentioned in the README
> > file.
> >
> > There are three files README, INSTALL, INSTALL.generic. When reading them,
> > they continue
> > referring around between themselves.
>
> The INSTALL.generic is "out of our control" it is the generic
> INSTALL file for autoconf/automake based packages. So we add
> a specific INSTALL file for the texinfo specifics in link with
> installing.
>
> > Can there be just one README (otherwise have just one INSTALL file) with
> > abbreviated
> > set of instructions of typical installation, at the beginning?
>
> I am not that convinced that it is a good idea. The reference to
> INSTALL appears at the beginning of the README and I think that INSTALL*
> are best separate as otherwise the INSTALL specific parts would get in the
> way of having a short README. As I said above, the INSTALL.generic is
> outside of our control, which makes the only real option merging the
> specific INSTALL in the README.
>
> > Thank you both for bearing with me. But it was not so clear and quick
> > about what exactly one should do when trying development versions.
>
> It is indeed not clear nor quick.
>
> It seems to me that README-hacking contains most of the information
> (though not about building in a different directory from the source),
> and then the INSTALL file. It is a bit scattered, but the problem is
> that different persons will not need the same information depending on
> where they come from and need to do (from a release, the developpment
> source, testing or installing). Also the overall build system is not
> simple, there is an intrinsic complexity that we can't really remove by
> instructions (the whole autoconf/automake/gettext, with two translated
> sets, and additionally some Makefile parts being generated).
>
> It is not so clear to me what/if we need to add more information, people
> testing from the development tree are very few, answering to questions
> by mail could be more efficient than trying to document everything.
>
> That being said, if you have specific ideas of changes to the files, do
> not hesitate to propose, in particular in the form of patches.
>
> >
>
> In general there is also a need to run
> ./autogen.sh
> in the source thee before going into the build directory.
>
> >
> > % mkdir build
> > % cd build
> > % srcdir/configure [options] [target]
> > % make
> > % make install
> > % cp srcdir/doc/texinfo.tex workdir
> >
> > Where workdir is the directory of your main Texinfo input file.
> >
> >
> >
> >
> > > Sent: Friday, December 04, 2020 at 10:53 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote:
> > > > > Sent: Friday, December 04, 2020 at 10:30 PM
> > > > > From: "Patrice Dumas"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > >
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> > > > > >
> > > > > > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > > > > > From: "Patrice Dumas"
> > > > > > > To: "Christopher Dimech"
> > > > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > > > >
> > > > > > > Subject: Re: Latest Development Version - @image with @value
> > > > > > >
> > > > > > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech
> > > > > > > wrote:
Re: Latest Development Version - @image with @value
I am still seeing version 2020-10-24.12 which you say is not the latest one Loading texinfo [version 2020-10-24.12] Have removed the old version from synaptic, and re-installed the one I got from the git repositor, downloaded texinfo.tex, and put that in the directories where I have the .texi files. And the problem remains. How is it that the installation from git still shows version 2020-10-24.12? > Sent: Friday, December 04, 2020 at 8:51 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 08:49:55PM +0100, Christopher Dimech wrote: > > Do you still think that the problem is with texinfo.tex? > > No, you just haven't installed the file properly. > > If you don't know where to copy the file, then putting it in the > same directory as your main Texinfo input file should work. >
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:30 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> >
> > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > I done the whole thing again, however the version is still showing
> > > >
> > > > Loading texinfo [version 2020-10-24.12]
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt /usr/local/bin/texi2pdf
> > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt
> > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > >
> > > You can look at the beginning of the file to check that it is indeed
> > > the latest one. If it is not used, it would be very strange.
> >
> > I see texinfo.tex is saying
> > \def\texinfoversion{2020-10-24.12}
>
> Then it is not the one from git, the one from git has
> \def\texinfoversion{2020-11-14.10}
That could be it. I got that from the website where it says
"latest texinfo.tex macro file"
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > kpsewhich --expand-var='$TEXINPUTS'
> > .:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> You have the standard path.
>
> --
> Pat
>
>
Re: Latest Development Version - @image with @value
Do you still think that the problem is with texinfo.tex?
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
Yes, I have done that. But you have said that I got texinfo [version
2020-10-24.12
using "git clone https://git.savannah.gnu.org/git/texinfo.git;.
Will install again, by doing another git clone.
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
Do not usually run configure in the same directory.
I make a build directory, then run configure from there.
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
I done the whole thing again, however the version is still showing
Loading texinfo [version 2020-10-24.12]
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
ls -lrt /usr/local/bin/texi2pdf
-rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
ls -lrt
-rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> Sent: Friday, December 04, 2020 at 6:28 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> You have to copy texinfo.tex manually to where it will be used.
> Running "make install" is not enough.
>
> On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> >
> > Have just re-downloaded the file and put in the directory
> > ~/01cuneus/tdr/03ch
> > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> >
> > To install the new version I ran gendocs.sh, then the usual configure etc.
> >
> > I can see that the programs were updated in /usr/local/bin/
> >
> > Problem remains
> > C*
> >
> > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > Using the following does not work for me. Do I require some setup?
> > > > Have
> > > > also got the latest texinfo.tex
> > > >
> > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > >
> > > > First call to @image works, the second fails.
> > >
> > > Well, I tried @image with @value with an absolute directory
> > > name, and it worked. What output are you getting from TeX? Are you
> > > sure the latest texinfo.tex is being read?
> > >
> > >
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:56 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 10:37:56PM +0100, Christopher Dimech wrote: > > > > That could be it. I got that from the website where it says > > "latest texinfo.tex macro file" > > This location is indeed used to do releases of texinfo.tex before the > whole texinfo package release, but it is still in general not as fresh > as the git file, especially when the changes are still being tested. > Understood. It would be extremely helpful to users trying to test or check the development version to put a remark about /doc/texinfo.tex in the section "Getting a Copy of the Git Repository". https://savannah.gnu.org/git/?group=texinfo > -- > Pat > >
Re: Latest Development Version - @image with @value
Fantastic. Things age working now. texinfo.tex is mentioned in the README
file.
There are three files README, INSTALL, INSTALL.generic. When reading them,
they continue
referring around between themselves.
Can there be just one README (otherwise have just one INSTALL file) with
abbreviated
set of instructions of typical installation, at the beginning?
Thank you both for bearing with me. But it was not so clear and quick
about what exactly one should do when trying development versions.
% mkdir build
% cd build
% srcdir/configure [options] [target]
% make
% make install
% cp srcdir/doc/texinfo.tex workdir
Where workdir is the directory of your main Texinfo input file.
> Sent: Friday, December 04, 2020 at 10:53 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:46:44PM +0100, Christopher Dimech wrote:
> > > Sent: Friday, December 04, 2020 at 10:30 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> > > >
> > > > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > > > From: "Patrice Dumas"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > > > >
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > > > I done the whole thing again, however the version is still showing
> > > > > >
> > > > > > Loading texinfo [version 2020-10-24.12]
> > > > > >
> > > > > > hagbard@fuckup:
> > > > > > + ~/01cuneus/tdr/03ch
> > > > > > ls -lrt /usr/local/bin/texi2pdf
> > > > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > > > >
> > > > > > hagbard@fuckup:
> > > > > > + ~/01cuneus/tdr/03ch
> > > > > > ls -lrt
> > > > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > > > >
> > > > > You can look at the beginning of the file to check that it is indeed
> > > > > the latest one. If it is not used, it would be very strange.
> > > >
> > > > I see texinfo.tex is saying
> > > > \def\texinfoversion{2020-10-24.12}
> > >
> > > Then it is not the one from git, the one from git has
> > > \def\texinfoversion{2020-11-14.10}
> >
> > I did a git clone. Where do you put the file? Apologies, but I cannot
> > determine
> > where texinfo.tex is located.
>
> It is in texinfo/doc/texinfo.tex
>
> --
> Pat
>
Re: Latest Development Version - @image with @value
Have just re-downloaded the file and put in the directory ~/01cuneus/tdr/03ch
(where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
To install the new version I ran gendocs.sh, then the usual configure etc.
I can see that the programs were updated in /usr/local/bin/
Problem remains
C*
> Sent: Friday, December 04, 2020 at 5:45 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Latest Development Version - @image with @value
>
> On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > Using the following does not work for me. Do I require some setup? Have
> > also got the latest texinfo.tex
> >
> > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> >
> > First call to @image works, the second fails.
>
> Well, I tried @image with @value with an absolute directory
> name, and it worked. What output are you getting from TeX? Are you
> sure the latest texinfo.tex is being read?
>
>
Re: Latest Development Version - @image with @value
This is what I have used git clone https://git.savannah.gnu.org/git/texinfo.git > Sent: Friday, December 04, 2020 at 6:16 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 05:57:41PM +0100, Christopher Dimech wrote: > > Let me check again. Any hints on how to know which one is being used? > > > > texi2pdf 03aCh-Chmed-html.texi > > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) > > (preloaded format=pdfetex) > > restricted \write18 enabled. > > entering extended mode > > > > (./03aCh-Chmed-html.texi (/home/hagbard/01cuneus/tdr/03ch/texinfo.tex > > Loading texinfo [version 2020-10-24.12]: pdf, fonts, markup, glyphs, > > It's this line here. The latest version is 2020-11-25.18. >
Re: Latest Development Version - @image with @value
I have tried that. Now I put the file in all directories where I have the all the texi files. Could you send me the file, so I can put the one you send. See what happens. > Sent: Friday, December 04, 2020 at 8:51 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Latest Development Version - @image with @value > > On Fri, Dec 04, 2020 at 08:49:55PM +0100, Christopher Dimech wrote: > > Do you still think that the problem is with texinfo.tex? > > No, you just haven't installed the file properly. > > If you don't know where to copy the file, then putting it in the > same directory as your main Texinfo input file should work. >
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:17 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > I done the whole thing again, however the version is still showing
> >
> > Loading texinfo [version 2020-10-24.12]
> >
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > ls -lrt /usr/local/bin/texi2pdf
> > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> >
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > ls -lrt
> > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
>
> You can look at the beginning of the file to check that it is indeed
> the latest one. If it is not used, it would be very strange.
I see texinfo.tex is saying
\def\texinfoversion{2020-10-24.12}
> An alternative possibility, but I doubt it a bit is if you have a non
> standard paths setting for TeX.
>
> I think that you can check your path with
>
> kpsewhich -show-path=tex
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
kpsewhich -show-path=tex
.:/home/hagbard/.texmf-config/tex/kpsewhich//:/home/hagbard/.texmf-var/tex/kpsewhich//:/home/hagbard/texmf/tex/kpsewhich//:/etc/texmf/tex/kpsewhich//:!!/var/lib/texmf/tex/kpsewhich//:!!/usr/local/share/texmf/tex/kpsewhich//:!!/usr/share/texmf/tex/kpsewhich//:!!/usr/share/texlive/texmf-dist/tex/kpsewhich//:/home/hagbard/.texmf-config/tex/generic//:/home/hagbard/.texmf-var/tex/generic//:/home/hagbard/texmf/tex/generic//:/etc/texmf/tex/generic//:!!/var/lib/texmf/tex/generic//:!!/usr/local/share/texmf/tex/generic//:!!/usr/share/texmf/tex/generic//:!!/usr/share/texlive/texmf-dist/tex/generic//:/home/hagbard/.texmf-config/tex///:/home/hagbard/.texmf-var/tex///:/home/hagbard/texmf/tex///:/etc/texmf/tex///:!!/var/lib/texmf/tex///:!!/usr/local/share/texmf/tex///:!!/usr/share/texmf/tex///:!!/usr/share/texlive/texmf-dist/tex///
> or
>
> kpsewhich --expand-var='$TEXINPUTS'
hagbard@fuckup:
+ ~/01cuneus/tdr/03ch
kpsewhich --expand-var='$TEXINPUTS'
.:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> >
> >
> >
> > > Sent: Friday, December 04, 2020 at 6:28 PM
> > > From: "Gavin Smith"
> > > To: "Christopher Dimech"
> > > Cc: "help-texinfo gnu"
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > You have to copy texinfo.tex manually to where it will be used.
> > > Running "make install" is not enough.
> > >
> > > On Fri, Dec 4, 2020 at 5:13 PM Christopher Dimech wrote:
> > > >
> > > > Have just re-downloaded the file and put in the directory
> > > > ~/01cuneus/tdr/03ch
> > > > (where the file resides) from where I run texi2pdf 03aCh-Chmed-html.texi
> > > >
> > > > To install the new version I ran gendocs.sh, then the usual configure
> > > > etc.
> > > >
> > > > I can see that the programs were updated in /usr/local/bin/
> > > >
> > > > Problem remains
> > > > C*
> > > >
> > > > > Sent: Friday, December 04, 2020 at 5:45 PM
> > > > > From: "Gavin Smith"
> > > > > To: "Christopher Dimech"
> > > > > Cc: "help-texinfo gnu"
> > > > > Subject: Re: Latest Development Version - @image with @value
> > > > >
> > > > > On Thu, Dec 03, 2020 at 08:03:19PM +0100, Christopher Dimech wrote:
> > > > > > Using the following does not work for me. Do I require some setup?
> > > > > > Have
> > > > > > also got the latest texinfo.tex
> > > > > >
> > > > > > @set igmpath /home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed
> > > > > > @image{/home/hagbard/01cuneus/tdr/ideogr/03bCh-Chmed/igc03-01-Sicl-CircAmRg.png}
> > > > > > @image{@value{igmpath}/igc03-01-Sicl-CircAmRg.png}
> > > > > >
> > > > > > First call to @image works, the second fails.
> > > > >
> > > > > Well, I tried @image with @value with an absolute directory
> > > > > name, and it worked. What output are you getting from TeX? Are you
> > > > > sure the latest texinfo.tex is being read?
> > > > >
> > > > >
> > >
> >
>
Re: Latest Development Version - @image with @value
> Sent: Friday, December 04, 2020 at 10:30 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "Gavin Smith" , "help-texinfo gnu"
>
> Subject: Re: Latest Development Version - @image with @value
>
> On Fri, Dec 04, 2020 at 10:22:34PM +0100, Christopher Dimech wrote:
> >
> > > Sent: Friday, December 04, 2020 at 10:17 PM
> > > From: "Patrice Dumas"
> > > To: "Christopher Dimech"
> > > Cc: "Gavin Smith" , "help-texinfo gnu"
> > >
> > > Subject: Re: Latest Development Version - @image with @value
> > >
> > > On Fri, Dec 04, 2020 at 07:14:42PM +0100, Christopher Dimech wrote:
> > > > I done the whole thing again, however the version is still showing
> > > >
> > > > Loading texinfo [version 2020-10-24.12]
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt /usr/local/bin/texi2pdf
> > > > -rwxr-xr-x 1 root root 1246 Dec 4 19:09 /usr/local/bin/texi2pdf
> > > >
> > > > hagbard@fuckup:
> > > > + ~/01cuneus/tdr/03ch
> > > > ls -lrt
> > > > -rw-rw-r-- 1 hagbard hagbard 380722 Dec 4 18:03 texinfo.tex
> > >
> > > You can look at the beginning of the file to check that it is indeed
> > > the latest one. If it is not used, it would be very strange.
> >
> > I see texinfo.tex is saying
> > \def\texinfoversion{2020-10-24.12}
>
> Then it is not the one from git, the one from git has
> \def\texinfoversion{2020-11-14.10}
I did a git clone. Where do you put the file? Apologies, but I cannot
determine
where texinfo.tex is located.
> > hagbard@fuckup:
> > + ~/01cuneus/tdr/03ch
> > kpsewhich --expand-var='$TEXINPUTS'
> > .:{/home/hagbard/.texmf-config,/home/hagbard/.texmf-var,/home/hagbard/texmf,/etc/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf,!!/usr/share/texlive/texmf-dist}/tex/{kpsewhich,generic,}//
>
> You have the standard path.
>
> --
> Pat
>
Re: @image for pdf and html
It has been figured that we cannot use the same file for both pdf/dvi output and html output. Because if the file has too many pixels, the image will be too big for html. We could end up with many calls to image with different files using @iftex and @ifhtml. > Sent: Tuesday, November 24, 2020 at 10:05 PM > From: "Gavin Smith" > To: daniela-s...@gmx.it > Cc: "help-texinfo gnu" > Subject: Re: @image for pdf and html > > On Tue, Nov 24, 2020 at 09:32:15PM +0100, daniela-s...@gmx.it wrote: > > What is your opinion on using the same image file name for > > both: (1) pdf, dvi; and (2) html. > > > > @image(file,w,h,alttext,.png) > > > > Meaning that html will search for the filename, but with a token being > > appended to it. > > Sorry, I don't understand the question. > > - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy
Re: @image for pdf and html
I am not sure, but can one pass file names to @image with @value? I remember that I could not do it when output is pdf or dvi. Have nat checked what happens for html output. Have also looked at @url, and found that it does not break at special characters as specified in the manual. Could users have something similar for break file names, as it is frequent that file names get very long, as happens with url's. Additionally, @float does not function. Regards Christopher - Christopher Dimech General Administrator - Naiad Informatics - GNU Project (Geocomputation) - Geophysical Simulation - Geological Subsurface Mapping - Disaster Preparedness and Mitigation - Natural Resource Exploration and Production - Free Software Advocacy > Sent: Tuesday, November 24, 2020 at 11:17 PM > From: daniela-s...@gmx.it > To: "Gavin Smith" > Cc: "help-texinfo gnu" > Subject: Re: @image for pdf and html > > > Sent: Tuesday, November 24, 2020 at 10:55 PM > > From: "Gavin Smith" > > To: "Christopher Dimech" > > Cc: "help-texinfo gnu" > > Subject: Re: @image for pdf and html > > > > On Tue, Nov 24, 2020 at 10:11:09PM +0100, Christopher Dimech wrote: > > > It has been figured that we cannot use the same file for both > > > pdf/dvi output and html output. Because if the file has too many > > > pixels, the image will be too big for html. We could end up with > > > many calls to image with different files using @iftex and @ifhtml. > > > > You could equally say it's too big for pdf, if the pdf is going to > > put online. It's the same image either way. > > It is html that is limiting resolution, thus capability must be discussed when > compared to pdf output. Html provides serious limitations, unlike in pdf > where you can select the width and height. In geology based manual, the > resolution > is the most important aspect of any image. > > > I don't see anything wrong with using conditionals for different > > output formats to specify different image files, if that is what > > is desired. > > There is nothing wrong. However geology based manuals inherently > have many images, and defining for both is an extremely cumbersome > proposition. Besides the fact that images in html have limited use > because of the number of pixel limitation. Otherwise you cannot > see the text. > > >
Re: Numbering Menu Items in html output
> Sent: Saturday, November 28, 2020 at 6:20 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "Patrice Dumas" > Subject: Re: Numbering Menu Items in html output > > Please send any queries to the public mailing lists > bug-texi...@gnu.org or help-texinfo@gnu.org. Missed the mailing list. Now I include it > On Sat, Nov 28, 2020 at 1:48 PM Christopher Dimech wrote: > > > > Have asked Eli to number the menu items for the "Emacs Lisp Reference > > Manual" > > who informed me that the menu gets unnumbered by Texinfo. > > > > Have done a test and can confirm. > > > > If one is using a Web Browser, it is much quicker to find if > > you say "See 10.4 Backquote". You just scroll to 10, then to > > four, rather than by a Brain Regexp. > > > > Regards > > Christopher > > > > > > > > >
