[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] B5 Page Setup
I would like to create a document using texinfo. Have created a texinfo file and would like to set the page to B5 and then set the margin widths. Then do texi2pdf. How can I do this change to the paper size?
[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?
Re: [help-texinfo] B5 Page Setup
Have tried using @pagesizes, however some ot the text on the right side is being cut off. > Sent: Thursday, October 12, 2017 at 8:35 AM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: [help-texinfo] B5 Page Setup > > > From: "Christopher Dimech" > > Date: Wed, 11 Oct 2017 23:09:57 +0200 > > Sensitivity: Normal > > > > I would like to create a document using texinfo. Have created a texinfo > > file and would > > like to set the page to B5 and then set the margin widths. Then do > > texi2pdf. How can I > > do this change to the paper size? > > You could use the @pagesizes command to specify the page dimensions. > See the description of that command in the Texinfo manual. >
[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] 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] Referencing Sections
Dear texinfo users, I would like to reference a section, but am unsure how to have it work in texinfo. For example in the following code, suppose @section will be given a section number of 4.4 by texinfo. I want to refer to the section by referring to section 4.4 ... ... also follow the conditions of section 4.4. ... @section Copying in Quantity @section Another Section
[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] User defined sectioning numbers when using @unnumbered
> I'm sorry, I don't get it. You want to have three different numbering > sequences in the table of contents: chapters, appendices, and other > license and copyright documents? That's correct. Have tried using @set and @value, and the trial worked as intended. Many thanks > Sent: Wednesday, January 02, 2019 at 8:09 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 07:52:12PM +0100, Christopher Dimech wrote: > > 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. > > I'm sorry, I don't get it. You want to have three different numbering > sequences in the table of contents: chapters, appendices, and other > license and copyright documents? > > > 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 > > The chapter structuring commands in the included file will follow the > numbering of the top-level file that is being included into. >
[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] 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] 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] 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] Using @listoffloats with @float contained in another file
I have written a document with two files. The main documents refers to labels
defined
in @float declarations in another file. However, when calling @listoffloats, no
details of floats are being displayed.
Example
---
\input texinfo
@c %**start of header
@smallbook
@finalout
@c %**end of header
@contents
@node list-of-figures
@unnumbered List of Figures
@listoffloats Figure
@c
@page
@node appendices
@unnumbered Appendices
@node umrq308E
@unnumberedsec E @ @ Executive Summary
@set insmas-umrq308E
@include ./umrq308E--ExecSm.texi
@bye
@c
In file ./umrq308E--ExecSm.texi
@set fignm fig-308E-a03
@float Figure,fig308Ea03
@center @image{./umrq3--files/E--ExecSm/308E--a03,13cm,,,.png}
@caption{Nomenclature for structure within Building 29.
@flushright
@* Label: @t{@value{fignm}}
@end flushright
}
@shortcaption{@emph{Not and Exit} required for blocked door B.}
@end float
[help-texinfo] Cross-References display undefined when using @include
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. Have tried to solve the problem by running "Compile and View" from emacs rather than the command line but I am getting the same problem.
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 @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? >
[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}
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. >
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
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.
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
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
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
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
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.
>
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
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? >
@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
@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*
@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
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
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
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 &optional 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
Anchors do not work with makeinfo
When I use an anchor, the link does not work when I use @ref when I run makeinfo
@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 >
Re: @menu puts too many restrictions to produce the .info file
Where are the customization variables documented? > 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 >
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: @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
Page Sizes B6 and C6
Dear Compeers, Because arbitrary page sizes do not function in texinfo, and because I would find small size pages like B6 and C6 extremely useful, could there be @bsixpaper and @csixpaper? Regards Christopher
Re: Page Sizes B6 and C6
Dear Gavin,
I've checked it out on (1) my Elisp Abbreviated Manual and (2) on one of
my technical manuals with mathematical expressions, equation numbers and
so on.
I approve of the results. Looks neat and margins relative to pagesize
look fantastic. Very good.
Thank you so very much
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: Thursday, October 22, 2020 at 9:51 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: Page Sizes B6 and C6
>
> On Thu, Oct 22, 2020 at 06:31:52PM +0200, Christopher Dimech wrote:
> > Dear Compeers,
> >
> > Because arbitrary page sizes do not function in texinfo, and because
> > I would find small size pages like B6 and C6 extremely useful, could
> > there be @bsixpaper and @csixpaper?
> >
> > Regards
> > Christopher
>
> Yes, maybe. This would be much more possible than supporting
> arbitrary paper sizes. I've tested the following definition of
> @bsixpaper:
>
> \def\bsixpaper{{\globaldefs = 1
> \afourpaper
> \internalpagesizes{140mm}{100mm}%
> {-6.35mm}{-12.7mm}%
> {\bindingoffset}{14pt}%
> {176mm}{125mm}%
> \globaldefs = 0
> }}
>
> and it seems to produce OK results, at least for some pages without
> hard-to-break lines. Could you give this a go and report if any of
> the parameters should be changed? You could use it by inserting
>
> @tex
> \gdef\bsixpaper{{\globaldefs = 1
> \afourpaper
> \internalpagesizes{140mm}{100mm}%
> {-6.35mm}{-12.7mm}%
> {\bindingoffset}{14pt}%
> {176mm}{125mm}%
> \globaldefs = 0
> }}
> @end tex
> @bsixpaper
>
> near the start of your input file.
>
>
@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
@ref without page numbers
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
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
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
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
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
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: @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,
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
>
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
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: @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
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. > > > > >
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 > >
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
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---
Installing Texinfo from Development Source Tree.
I am trying to install texinfo using the development source tree. git clone https://git.savannah.gnu.org/git/texinfo.git I am having problem with the configure part. There is no configure and am trying to build it.
Re: Installing Texinfo from Development Source Tree.
I am getting the following complaining of makeinfo. Have installed Gnu Make WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: <http://www.gnu.org/software/texinfo/> The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: <http://www.gnu.org/software/make/> make[2]: *** [Makefile:1368: texinfo-js.info] Error 127 make[2]: Leaving directory '/home/hagbard/GAdmBuild/texinfo/js' make[1]: *** [Makefile:1379: all-recursive] Error 1 make[1]: Leaving directory '/home/hagbard/GAdmBuild/texinfo' Makefile:1318: recipe for target 'all' failed make: *** [all] Error 2 > Sent: Friday, October 30, 2020 at 9:13 PM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Installing Texinfo from Development Source Tree. > > > From: Christopher Dimech > > Date: Fri, 30 Oct 2020 21:02:40 +0100 > > Sensitivity: Normal > > > > I am trying to install texinfo using the development source tree. > > > > git clone https://git.savannah.gnu.org/git/texinfo.git > > > > I am having problem with the configure part. There is no configure and am > > trying to build it. > > Run autogen.sh, it should create the configure script. >
Re: Installing Texinfo from Development Source Tree.
It did not complain this time round. Thank you. > Sent: Friday, October 30, 2020 at 10:02 PM > From: "Eli Zaretskii" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Installing Texinfo from Development Source Tree. > > > From: Christopher Dimech > > Cc: help-texinfo@gnu.org > > Date: Fri, 30 Oct 2020 21:45:58 +0100 > > Sensitivity: Normal > > > > I am getting the following complaining of makeinfo. > > Install some official release of Texinfo, and then try again. >
Development Tree lacking @bsixpaper
Am trying the Development Tree and I thought the version would now have @bsixpaper, @bsixpaper, ... Regards C*
Texinfo Image Re-Scaling for Papersize
Recently small page sizes (e.g. @bsixpaper) was added. I have some documents with images of a certain size for B5 Paper, which get too large and some parts get of the image gets cut off. Could Texinfo be made to adjust the image size accordingly as is done with text to fit smaller pages. How about a flag that telling Texinfo the dafault paper size to use for the height and width of the image. Then if a user needs to use a smaller paper size. the height and width get re-scaled according to the smaller or larger paper size. C*
Re: Development Tree lacking @bsixpaper
I did the following command and installed. git clone https://git.savannah.gnu.org/git/texinfo.git I did the following and seeme good. Did I get the wrong one? texi2pdf -v texi2dvi (GNU Texinfo 6.7dev) Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. > Sent: Saturday, October 31, 2020 at 11:16 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Development Tree lacking @bsixpaper > > On Fri, Oct 30, 2020 at 10:33:16PM +0100, Christopher Dimech wrote: > > Am trying the Development Tree and I thought the version would now have > > @bsixpaper, > > @bsixpaper, ... > > > > Regards > > C* > > > > It does. >
Re: Development Tree lacking @bsixpaper
> Sent: Saturday, October 31, 2020 at 12:25 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: help-texinfo@gnu.org > Subject: Re: Development Tree lacking @bsixpaper > > On Sat, Oct 31, 2020 at 12:04:28PM +0100, Christopher Dimech wrote: > > @bsixpaper works if I put texinfo.texi in the local directory. > > > > When using @smallbook, I get smallbook, but when I remove > > @smallbook and call @bsixpaper, I am getting @afourpaper > > > > > > @ifclear InclFl--Chmed > > \input texinfo > > @set TlPage--Chmed > > @set FMatr--Chmed > > @set NoShow--Chmed--Igm > > @set Show--Chmed--Rfc > > @set Show--Chmed--FLic > > @end ifclear > > > > @c %**start of header > > @ifset TlPage--Chmed > > @setfilename Chmed.info > > @settitle Chmed > > @c @smallbook > > @bsixpaper > > @finalout > > @end ifset > > @c %**end of header > > You mean texinfo.tex. C* Correct > > Yes, you have to install that file manually where TeX will find it. > C* But when there is an official release, one would not need to store locally. Am I right? I never used to put the file in local directory for official releases before.
Re: Texinfo Image Re-Scaling for Papersize
I can see your point. > Sent: Saturday, October 31, 2020 at 12:01 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Texinfo Image Re-Scaling for Papersize > > On Sat, Oct 31, 2020 at 10:37:33AM +0100, Christopher Dimech wrote: > > > > Recently small page sizes (e.g. @bsixpaper) was added. I have some > > documents > > with images of a certain size for B5 Paper, which get too large and some > > parts > > get of the image gets cut off. > > > > Could Texinfo be made to adjust the image size accordingly as is done with > > text > > to fit smaller pages. How about a flag that telling Texinfo the dafault > > paper > > size to use for the height and width of the image. Then if a user needs to > > use > > a smaller paper size. the height and width get re-scaled according to the > > smaller > > or larger paper size. > > > > I don't think it could work. Some images may be fine without > rescaling, just taking up a larger percentage of the page. Some images > may be too small if they are scalead; for example, diagrams with > small details. Only the document author can know whether an image > should be scaled, and by how much. > > Did you experiment with the WIDTH and HEIGHT parameters to @image? >
Re: Development Tree lacking @bsixpaper
I usually want to use the most recent source code when preparing for my releases. That helps make improvements at a much earlier time, and thusly be able to release a better product that works better as users start updating the associated packages later on. - 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: Saturday, October 31, 2020 at 7:29 PM > From: "Patrice Dumas" > To: "Christopher Dimech" > Cc: "Gavin Smith" , help-texinfo@gnu.org > Subject: Re: Development Tree lacking @bsixpaper > > On Sat, Oct 31, 2020 at 12:35:42PM +0100, Christopher Dimech wrote: > > > > C* But when there is an official release, one would not need to > > store locally. Am I right? I never used to put the file in local > > directory for official releases before. > > I am not sure how you got the new releases before, but in most cases > people do not build and install texinfo from source by themselves, and > those who do also install texinfo.tex manually. In most cases, texinfo > is packaged as part of a packaging system, which depends on the platform > and most users get new versions like that. In general, users willing to > test/use prereleases may install from source, but it probably amounts to > a small number of people. > > -- > Pat >
Re: @menu puts too many restrictions to produce the .info file
Good evening Gavin. I have actually. My original plan was to have multiple menus for different types of users, so they may traverse it according to the job they want to do. Many, including myself end up having to go though a lot of menu paths to get what I need. So it is customary for me to simply take the texi files and traverse using some scripts rather than using info. I used to use Next/Prev/Up, although a bit tedious to specify three things for each node. Much rather have a switch that lets me set any menu the way I want without starting whining at me. Not everybody requires the same level of detail and for some users, many nodes would be irrelevant for them. As a workaround I been making nodes with a sort of "menu" but really using @ref for the links. Does my wrangling make sense, or do you see problems in using info in the said way? Info works well, until you start focusing on abbreviated ways of doing a job and you got to use the manual. There are some packages with just an info manual which I find difficult to use. I prefer html entirely on one page for rapidity. - 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: Saturday, October 31, 2020 at 10:04 PM > From: "Gavin Smith" > To: "Patrice Dumas" , "Christopher Dimech" > , "help-texinfo gnu" > Subject: Re: @menu puts too many restrictions to produce the .info file > > On Tue, Oct 20, 2020 at 05:59:56PM +0100, Gavin Smith wrote: > > On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote: > > > If an author wants to have irregular menu or node structures for some > > > reason (I haven't made sense exactly of what Christopher is doing > > > with his documents) then they could use explicit node pointers, > > > specifying Next/Prev/Up for each node. > > > > Another idea is to make it so that if a node has explicit node > > pointers, then its menu would not be used to determine structural > > relations between nodes. The menu, along with the node pointers, would > > be trusted to be correct, and intended by the author, but not used > > for anything else. > > Did you think about whether this would be a good idea? I explained > this in more detail in another message. >
TOC cuts long titles in middle for texi2pdf
Have noticed that in the TOC, when a @subsection title is long, the title is cut in the middle rather than continuing a bit before the Page Number, then wrapping the remaining words on the next line when using texi2pdf. @subsection Easiest way to pass a Numeric Argument using Universal Prefix texi2pdf file.texi 1.5 Firing Commands with Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5.1 Easiest way to pass a Numeric Argument using Universal Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 --
Re: TOC cuts long titles in middle for texi2pdf
To cut it from the word that would not fit by a spacing of say two dots from the page number. However, if that would result in just one word, cut it such that there are at least two or three words Example: From This > > > > 1.5 Firing Commands with Arguments . . . . . . . . . 9 > > 1.5.1 Easiest way to pass a Numeric >> Argument using Universal Prefix. . . . . . . . . 10 > > -- To This (which also gives indication of a long title) > > > > 1.5 Firing Commands with Arguments . . . . . . . . . 9 > > 1.5.1 Easiest way to pass a Numeric Argument using >> Universal Prefix . . . . . . . . . . . . . . . . 10 > > -- > Sent: Monday, November 02, 2020 at 10:17 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: TOC cuts long titles in middle for texi2pdf > > On Mon, Nov 02, 2020 at 10:01:23PM +0100, Christopher Dimech wrote: > > > > Have noticed that in the TOC, when a @subsection title > > is long, the title is cut in the middle rather than > > continuing a bit before the Page Number, then wrapping > > the remaining words on the next line when using texi2pdf. > > > > @subsection Easiest way to pass a Numeric Argument using Universal Prefix > > > > texi2pdf file.texi > > > > > > 1.5 Firing Commands with Arguments . . . . . . . . . . . . . . . . . . . . > > . . . . . . . . . . 9 > > 1.5.1 Easiest way to pass a Numeric > > Argument using Universal Prefix . . . . . . . . . . . . . . . . . . . . . . > > . . . . . . . . 10 > > -- > > What is wrong with this? The title has to be cut somewhere if it is > too long. > >
Re: TOC cuts long titles in middle for texi2pdf
Can cutting be done this way? It is not as the simplistic operation as cutting by half. Regards Christopher > Sent: Monday, November 02, 2020 at 10:33 PM > From: "Christopher Dimech" > To: "Gavin Smith" > Cc: "help-texinfo gnu" > Subject: Re: TOC cuts long titles in middle for texi2pdf > > To cut it from the word that would not fit by a spacing of say two dots from > the page > number. However, if that would result in just one word, cut it such that > there are at > least two or three words > > Example: > > From This > > > > > > > 1.5 Firing Commands with Arguments . . . . . . . . . 9 > > > 1.5.1 Easiest way to pass a Numeric > >> Argument using Universal Prefix. . . . . . . . . 10 > > > -- > > To This (which also gives indication of a long title) > > > > > > > 1.5 Firing Commands with Arguments . . . . . . . . . 9 > > > 1.5.1 Easiest way to pass a Numeric Argument using > >> Universal Prefix . . . . . . . . . . . . . . . . 10 > > > -- > > > Sent: Monday, November 02, 2020 at 10:17 PM > > From: "Gavin Smith" > > To: "Christopher Dimech" > > Cc: "help-texinfo gnu" > > Subject: Re: TOC cuts long titles in middle for texi2pdf > > > > On Mon, Nov 02, 2020 at 10:01:23PM +0100, Christopher Dimech wrote: > > > > > > Have noticed that in the TOC, when a @subsection title > > > is long, the title is cut in the middle rather than > > > continuing a bit before the Page Number, then wrapping > > > the remaining words on the next line when using texi2pdf. > > > > > > @subsection Easiest way to pass a Numeric Argument using Universal Prefix > > > > > > texi2pdf file.texi > > > > > > > > > 1.5 Firing Commands with Arguments . . . . . . . . . . . . . . . . . . . > > > . . . . . . . . . . . 9 > > > 1.5.1 Easiest way to pass a Numeric > > > Argument using Universal Prefix . . . . . . . . . . . . . . . . . . . . . > > > . . . . . . . . . 10 > > > -- > > > > What is wrong with this? The title has to be cut somewhere if it is > > too long. > > > > > >
Re: TOC cuts long titles in middle for texi2pdf
If the line is long, I do see that it would be more readable to have a length with no dots, to show the line continues on the next line. I have not seen that it was splitting 70%/30%. We can stick with 70%/30%. > Sent: Saturday, November 07, 2020 at 3:22 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: TOC cuts long titles in middle for texi2pdf > > On Sat, Nov 07, 2020 at 01:23:00PM +0100, Christopher Dimech wrote: > > Can cutting be done this way? It is not as the simplistic operation > > as cutting by half. > > > > Regards > > Christopher > > Maybe but this part of the code is complicated and it would risk > making it worse in other cases. There are test cases in > texinfo-tex-test.texi in the Texinfo repository which you could try > with different configurations. > > Currently, it attempts to split the line roughly 70%/30% in length. > (See \finishentry in texinfo.tex). It is probably not possible to do > it by word count. > > I think the first line should be longer than the second line, but > apart from that I am not convinced that it looks better to have the > first line longer. A more even split may be more readable. >
@macro to accept hyphen
Would it be possible to allow macro names to use hyphens? @macro Regexp-EsnStruct Body @end macro
Re: @macro to accept hyphen
I have seen that mathematical expressions are not displayed when called within a macro. @macro Regu @tex \alpha @end tex @end macro @Regu @tex \beta @end tex > Sent: Saturday, November 07, 2020 at 10:38 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @macro to accept hyphen > > On Sat, Nov 07, 2020 at 08:23:50PM +0100, Christopher Dimech wrote: > > Would it be possible to allow macro names to use hyphens? > > > > @macro Regexp-EsnStruct > > Body > > @end macro > > It's a reasonable question, but it could cause horrendous problems > with TeX. There is already special treatment of hyphens in various > contexts (monospaced font, URL's, etc.) and trying to support hyphens > in macro names could easily break in one of these contexts. In fact, > digits are not even supported: only the 26 lower-case letters and 26 > upper-case letters. >
Re: @macro to accept hyphen
Did not know about the doubling \\. How is that? Could you include an example
of a macro with Mathematical expression? Have written an example for you.
@macro Mtk
@tex
In spherical coordinates, the Laplacian Operator is $\\nabla^2 \\phi(r)$.
$$\\nabla^2 \\phi(r) =
{1 \\over r^2} {\\partial \\over \\partial r}
\\bigg\\lbrack r^2 {\\partial \\phi \\over \\partial r}\\bigg\\rbrack$$
@end tex
@end macro
@Mtk
> Sent: Saturday, November 07, 2020 at 11:47 PM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @macro to accept hyphen
>
> On Sat, Nov 07, 2020 at 11:29:54PM +0100, Christopher Dimech wrote:
> >
> > I have seen that mathematical expressions are not displayed
> > when called within a macro.
> >
> > @macro Regu
> > @tex
> > \alpha
> > @end tex
> > @end macro
> >
> > @Regu
> >
> > @tex
> > \beta
> > @end tex
>
> \alpha and \beta need to be in math mode, and the macro works OK if
> you double the backslash.
>
>
> @macro Regu
> @tex
> $\\alpha$
> @end tex
> @end macro
>
> @Regu
>
> @tex
> $\beta$
> @end tex
>
>
Re: @macro to accept hyphen
Have not seen a mathematical expression in the manual. Thusly I have provided
you with one. Works perfectly, no problem with it.
You have this sentence in the macro.
To get a single ‘\’ in the macro expansion, use ‘\\’
Although the information is there, it is very cryptic. If we include an
indented
example with a real math expression, users will be immediately drawn to it.
> Sent: Sunday, November 08, 2020 at 10:02 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @macro to accept hyphen
>
> On Sun, Nov 08, 2020 at 01:15:06AM +0100, Christopher Dimech wrote:
> > Did not know about the doubling \\. How is that?
>
> It's explained in the manual.
>
> > Could you include an example
> > of a macro with Mathematical expression? Have written an example for you.
> >
> >
> > @macro Mtk
> > @tex
> > In spherical coordinates, the Laplacian Operator is $\\nabla^2 \\phi(r)$.
> > $$\\nabla^2 \\phi(r) =
> > {1 \\over r^2} {\\partial \\over \\partial r}
> > \\bigg\\lbrack r^2 {\\partial \\phi \\over \\partial r}\\bigg\\rbrack$$
> > @end tex
> > @end macro
> >
> > @Mtk
>
> Your example works perfectly; what is the problem with it?
>
@bnumpaper , @cnumpaper
Dear Gavin,
The modifications for the new @bsixpaper have been made to texinfo.tex.
Are you planning to change the source code, or will the changes be kept
in texinfo.tex for the next release?
> Sent: Sunday, November 08, 2020 at 10:02 AM
> From: "Gavin Smith"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @macro to accept hyphen
>
> On Sun, Nov 08, 2020 at 01:15:06AM +0100, Christopher Dimech wrote:
> > Did not know about the doubling \\. How is that?
>
> It's explained in the manual.
>
> > Could you include an example
> > of a macro with Mathematical expression? Have written an example for you.
> >
> >
> > @macro Mtk
> > @tex
> > In spherical coordinates, the Laplacian Operator is $\\nabla^2 \\phi(r)$.
> > $$\\nabla^2 \\phi(r) =
> > {1 \\over r^2} {\\partial \\over \\partial r}
> > \\bigg\\lbrack r^2 {\\partial \\phi \\over \\partial r}\\bigg\\rbrack$$
> > @end tex
> > @end macro
> >
> > @Mtk
>
> Your example works perfectly; what is the problem with it?
>
Re: @bnumpaper , @cnumpaper
Gavin, I can take care of putting the various page sizes and test them if you guide me through the code. We all got to be useful eventually. Regards Christopher > Sent: Sunday, November 08, 2020 at 6:37 PM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: @bnumpaper , @cnumpaper > > On Sun, Nov 08, 2020 at 03:23:05PM +0100, Christopher Dimech wrote: > > > > Dear Gavin, > > > > The modifications for the new @bsixpaper have been made to texinfo.tex. > > Are you planning to change the source code, or will the changes be kept > > in texinfo.tex for the next release? > > I plan on keeping @bsixpaper in. >
Re: @macro to accept hyphen
> Sent: Monday, November 09, 2020 at 10:22 PM > From: "Patrice Dumas" > To: "Gavin Smith" > Cc: "Christopher Dimech" , "help-texinfo gnu" > > Subject: Re: @macro to accept hyphen > > On Mon, Nov 09, 2020 at 08:07:02PM +, Gavin Smith wrote: > > On Sun, Nov 08, 2020 at 10:56:46AM +0100, Christopher Dimech wrote: > > > Have not seen a mathematical expression in the manual. Thusly I have > > > provided > > > you with one. Works perfectly, no problem with it. > > > > > > You have this sentence in the macro. > > > > > > To get a single ‘\’ in the macro expansion, use ‘\\’ > > > > > > Although the information is there, it is very cryptic. If we include an > > > indented > > > example with a real math expression, users will be immediately drawn to > > > it. > > > > I don't know if your use of math inside macros is likely to be > > prevalent enough to warrant special mention. In many Gnu Packages, much math expressions are not necessary. But will become more prevalent as more work is done on geophysical software (e.g., Gnu Behistun). > I think that a special mention would stil be good even if it is likely > that math in a macro is not prevalent, as it is probably the main case > with \ appearing naturally in text. Yep, it is very natural and a good example for many who want to use math expressions. Macros become important for fundamental expressions that occur frequently in a given field because they would have the advantage of simply calling them using popular names. > -- > Pat >
Re: Paper Sizes
The sizes are useful to display short notes, mathematical expressions, and Code Snippets, that look large on screen (i.e. font size against paper size). This will alleviate the time spent writing notes for display to an audience or for video communication purposes. Having things redone so they get displayed with Libre Office or whatever is a waste of time for many people who customarily write their documentation and notes in Texinfo. We can just insert named macros wihout having to read and decipher what the mathematical expressions are about. When working with many mathematical expressions it is easy to be overwhelmed by the many symbols of tex. The display has many similarities to how Edward Witten and Cedric Villani use computers for mathematical display in meetings. Working with Texinfo to do my work, using Texinfo to also write short notes would be very useful because many would not need to do additional work. Regards Christopher > Sent: Wednesday, November 11, 2020 at 8:29 AM > From: "Gavin Smith" > To: "Christopher Dimech" > Cc: "help-texinfo gnu" > Subject: Re: Paper Sizes > > On Wed, Nov 11, 2020 at 04:29:41AM +0100, Christopher Dimech wrote: > > Dear Gavin, > > > > I have been working on the paper sizes (B5, B6, B7, B8, C5, C6, C7,C8) so > > we can > > include them. Have set the Paper Sizes and the Text Area. > > > > Perhaps you can improve on the heading spacing (for a smaller one), > > etc. Let me know what you think. > > > > Regards > > Christopher > > Thanks for looking at this. > > I am not sure that there is any need for support of the C series as > this is mainly used for envelopes, I gather, not so much for paper > itself. > > B6 seemed like a good idea as it looked the right size for a small > paperback book. B8 is tiny, though. I still don't understand what > you are doing with changing the page size. I think that more paper > sizes could be added if they were going to be used for printing on. > > >
