Attachment 712806 Details for Bug 923365 – A patch to let xemacs build with texinfo >= 5.0

[patch] A patch to let xemacs build with texinfo >= 5.0

xemacs-21.5.33-texinfo5.patch (text/plain), 16.89 KB, created by Ralf Corsepius on 2013-03-19 16:57:11 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ralf Corsepius

Created: 2013-03-19 16:57:11 UTC

Size: 16.89 KB

patch

obsolete

>diff -Naur xemacs-21.5.33.orig/man/internals/internals.texi xemacs-21.5.33/man/internals/internals.texi
>--- xemacs-21.5.33.orig/man/internals/internals.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/internals/internals.texi	2013-03-19 10:52:11.017962792 +0100
>@@ -21337,7 +21337,7 @@
> 
> 
> @node Ben's separate stderr notes,  , Subprocesses, Subprocesses
>-@subsection Ben's separate stderr notes (probably obsolete)
>+@section Ben's separate stderr notes (probably obsolete)
> 
> This node contains some notes that Ben kept on his separate subprocess
> workspace.  These notes probably describe changes and features that have
>diff -Naur xemacs-21.5.33.orig/man/lispref/edebug-inc.texi xemacs-21.5.33/man/lispref/edebug-inc.texi
>--- xemacs-21.5.33.orig/man/lispref/edebug-inc.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/lispref/edebug-inc.texi	2013-03-19 10:52:11.019962823 +0100
>@@ -1103,7 +1103,7 @@
> Here is a table of the possibilities for @var{specification} and how each
> directs processing of arguments.
> 
>-@table @bullet
>+@itemize @bullet
> 
> @item @code{t}
> All arguments are instrumented for evaluation.
>@@ -1120,7 +1120,7 @@
> The elements of the list describe the types of the arguments of a
> calling form.  The possible elements of a specification list are
> described in the following sections.
>-@end table
>+@end itemize
> 
> @menu
> * Specification List::		How to specify complex patterns of evaluation.
>diff -Naur xemacs-21.5.33.orig/man/lispref/packaging.texi xemacs-21.5.33/man/lispref/packaging.texi
>--- xemacs-21.5.33.orig/man/lispref/packaging.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/lispref/packaging.texi	2013-03-19 10:52:11.019962823 +0100
>@@ -600,7 +600,7 @@
> Does most of the work.  Builds the elcs, infos at a minimum.
> @end table
> 
>-@subsection The targets that most people would be interested in would be:
>+@section The targets that most people would be interested in would be:
> 
> @itemize @bullet
> @item @code{all}
>diff -Naur xemacs-21.5.33.orig/man/texinfo/texinfo.texi xemacs-21.5.33/man/texinfo/texinfo.texi
>--- xemacs-21.5.33.orig/man/texinfo/texinfo.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/texinfo/texinfo.texi	2013-03-19 10:59:38.465905138 +0100
>@@ -13717,14 +13717,14 @@
> @item US-ASCII
> This has no particular effect, but it's included for completeness.
> 
>-@itemx UTF-8
>+@item UTF-8
> The vast global character encoding, expressed in 8-bit bytes.
> The Texinfo processors have no deep knowledge of Unicode; for the most
> part, they just pass along the input they are given to the output.
> 
>-@itemx ISO-8859-1
>+@item ISO-8859-1
> @itemx ISO-8859-15
>-@item ISO-8859-2
>+@itemx ISO-8859-2
> These specify the standard encodings for Western European (the first
> two) and Eastern European languages (the third), respectively.  ISO
> 8859-15 replaces some little-used characters from 8859-1 (e.g.,
>@@ -17428,7 +17428,7 @@
> Generate the uppercase and lowercase AE ligatures, respectively:
> @AE{}, @ae{}.  @xref{Inserting Accents}.
> 
>-@itemx @@afivepaper
>+@item @@afivepaper
> Change page dimensions for the A5 paper size.  @xref{A4 Paper}.
> 
> @item @@afourlatex
>@@ -17955,7 +17955,7 @@
> the corresponding @code{@@end ifnot@var{format}}.
> @xref{Conditionals}.
> 
>-@itemx @@ifnotinfo
>+@item @@ifnotinfo
> Begin text to appear in output other than Info and (for historical
> compatibility) plain text.  Pair with @code{@@end ifnotinfo}.
> @xref{Conditionals}.
>diff -Naur xemacs-21.5.33.orig/man/widget.texi xemacs-21.5.33/man/widget.texi
>--- xemacs-21.5.33.orig/man/widget.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/widget.texi	2013-03-19 11:57:24.009741188 +0100
>@@ -120,7 +120,7 @@
> 
> @node  Introduction, User Interface, Top, Top
> @comment  node-name,  next,  previous,  up
>-@section Introduction
>+@chapter Introduction
> 
> @c XEmacs changes to reflect history, native widgets, and GTK
> Most graphical user interface toolkits provide
>@@ -234,7 +234,7 @@
> 
> @node User Interface, Programming Example, Introduction, Top
> @comment  node-name,  next,  previous,  up
>-@section User Interface
>+@chapter User Interface
> 
> A form consists of read only text for documentation and some fields,
> where each field contains two parts, a tag and a value.  The tags are
>@@ -280,7 +280,7 @@
> within a form, namely editing the editable text fields and activating
> the buttons.
> 
>-@subsection Editable Text Fields
>+@section Editable Text Fields
> 
> In the example, the value for the @samp{Name} is most likely displayed
> in an editable text field, and so are values for each of the members of
>@@ -317,7 +317,7 @@
> Face used for other editing fields.
> @end deffn
> 
>-@subsection Buttons
>+@section Buttons
> 
> @cindex widget buttons
> @cindex button widgets
>@@ -388,7 +388,7 @@
> it.
> @end defopt
> 
>-@subsection Navigation
>+@section Navigation
> 
> You can use all the normal Emacs commands to move around in a form
> buffer, plus you will have these additional commands:
>@@ -407,7 +407,7 @@
> 
> @node Programming Example, Setting Up the Buffer, User Interface, Top
> @comment  node-name,  next,  previous,  up
>-@section Programming Example
>+@chapter Programming Example
> 
> @cindex widgets, programming example
> @cindex example of using widgets
>@@ -503,7 +503,7 @@
> 
> @node Setting Up the Buffer, Basic Types, Programming Example, Top
> @comment  node-name,  next,  previous,  up
>-@section Setting Up the Buffer
>+@chapter Setting Up the Buffer
> 
> Widgets are created with @code{widget-create}, which returns a
> @dfn{widget} object.  This object can be queried and manipulated by
>@@ -558,7 +558,7 @@
> 
> @node Basic Types, Sexp Types, Setting Up the Buffer, Top
> @comment  node-name,  next,  previous,  up
>-@section Basic Types
>+@chapter Basic Types
> 
> This is the general syntax of a type specification:
> 
>@@ -803,7 +803,7 @@
> 
> @node link, url-link, Basic Types, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{link} Widget
>+@section The @code{link} Widget
> @findex link@r{ widget}
> 
> Syntax:
>@@ -828,7 +828,7 @@
> 
> @node url-link, info-link, link, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{url-link} Widget
>+@section The @code{url-link} Widget
> @findex url-link@r{ widget}
> 
> Syntax:
>@@ -843,7 +843,7 @@
> 
> @node info-link, push-button, url-link, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{info-link} Widget
>+@section The @code{info-link} Widget
> @findex info-link@r{ widget}
> 
> Syntax:
>@@ -857,7 +857,7 @@
> 
> @node  push-button, editable-field, info-link, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{push-button} Widget
>+@section The @code{push-button} Widget
> @findex push-button@r{ widget}
> 
> Syntax:
>@@ -882,7 +882,7 @@
> 
> @node editable-field, text, push-button, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{editable-field} Widget
>+@section The @code{editable-field} Widget
> @findex editable-field@r{ widget}
> 
> Syntax:
>@@ -934,7 +934,7 @@
> 
> @node text, menu-choice, editable-field, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{text} Widget
>+@section The @code{text} Widget
> @findex text@r{ widget}
> 
> @vindex widget-text-keymap
>@@ -944,7 +944,7 @@
> 
> @node menu-choice, radio-button-choice, text, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{menu-choice} Widget
>+@section The @code{menu-choice} Widget
> @findex menu-choice@r{ widget}
> 
> Syntax:
>@@ -985,7 +985,7 @@
> 
> @node radio-button-choice, item, menu-choice, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{radio-button-choice} Widget
>+@section The @code{radio-button-choice} Widget
> @findex radio-button-choice@r{ widget}
> 
> Syntax:
>@@ -1052,7 +1052,7 @@
> 
> @node item, choice-item, radio-button-choice, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{item} Widget
>+@section The @code{item} Widget
> @findex item@r{ widget}
> 
> Syntax:
>@@ -1067,7 +1067,7 @@
> 
> @node choice-item, toggle, item, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{choice-item} Widget
>+@section The @code{choice-item} Widget
> @findex choice-item@r{ widget}
> 
> Syntax:
>@@ -1084,7 +1084,7 @@
> 
> @node toggle, checkbox, choice-item, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{toggle} Widget
>+@section The @code{toggle} Widget
> @findex toggle@r{ widget}
> 
> Syntax:
>@@ -1117,7 +1117,7 @@
> 
> @node checkbox, checklist, toggle, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{checkbox} Widget
>+@section The @code{checkbox} Widget
> @findex checkbox@r{ widget}
> 
> This widget has two possible states, @samp{selected} and
>@@ -1131,7 +1131,7 @@
> 
> @node checklist, editable-list, checkbox, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{checklist} Widget
>+@section The @code{checklist} Widget
> @findex checklist@r{ widget}
> 
> Syntax:
>@@ -1189,7 +1189,7 @@
> 
> @node editable-list, group, checklist, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{editable-list} Widget
>+@section The @code{editable-list} Widget
> @findex editable-list@r{ widget}
> 
> Syntax:
>@@ -1247,7 +1247,7 @@
> 
> @node group,  , editable-list, Basic Types
> @comment  node-name,  next,  previous,  up
>-@subsection The @code{group} Widget
>+@section The @code{group} Widget
> @findex group@r{ widget}
> 
> This widget simply groups other widgets together.
>@@ -1262,7 +1262,7 @@
> 
> @node Sexp Types, Widget Properties, Basic Types, Top
> @comment
>-@section Sexp Types
>+@chapter Sexp Types
> @cindex sexp types
> 
> A number of widgets for editing @dfn{s-expressions} (Lisp types), sexp
>@@ -1278,7 +1278,7 @@
> 
> @node constants, generic, Sexp Types, Sexp Types
> @comment  node-name,  next,  previous,  up
>-@subsection The Constant Widgets
>+@section The Constant Widgets
> @cindex constant widgets
> 
> The @code{const} widget can contain any Lisp expression, but the user is
>@@ -1315,7 +1315,7 @@
> 
> @node generic, atoms, constants, Sexp Types
> @comment  node-name,  next,  previous,  up
>-@subsection Generic Sexp Widget
>+@section Generic Sexp Widget
> @cindex generic sexp widget
> 
> The @code{sexp} widget can contain any Lisp expression, and allows the
>@@ -1337,7 +1337,7 @@
> 
> @node atoms, composite, generic, Sexp Types
> @comment  node-name,  next,  previous,  up
>-@subsection Atomic Sexp Widgets
>+@section Atomic Sexp Widgets
> @cindex atomic sexp widget
> 
> The atoms are s-expressions that do not consist of other s-expressions.
>@@ -1415,7 +1415,7 @@
> 
> @node composite,  , atoms, Sexp Types
> @comment  node-name,  next,  previous,  up
>-@subsection Composite Sexp Widgets
>+@section Composite Sexp Widgets
> @cindex composite sexp widgets
> 
> The syntax for the composite widget construct is:
>@@ -1517,7 +1517,7 @@
> 
> @node Widget Properties, Defining New Widgets, Sexp Types, Top
> @comment  node-name,  next,  previous,  up
>-@section Properties
>+@chapter Properties
> @cindex properties of widgets
> @cindex widget properties
> 
>@@ -1612,7 +1612,7 @@
> 
> @node Defining New Widgets, Widget Browser, Widget Properties, Top
> @comment  node-name,  next,  previous,  up
>-@section Defining New Widgets
>+@chapter Defining New Widgets
> @cindex new widgets
> @cindex defining new widgets
> 
>@@ -1856,7 +1856,7 @@
> 
> @node Widget Browser, Widget Minor Mode, Defining New Widgets, Top
> @comment  node-name,  next,  previous,  up
>-@section Widget Browser
>+@chapter Widget Browser
> @cindex widget browser
> 
> There is a separate package to browse widgets.  This is intended to help
>@@ -1881,7 +1881,7 @@
> 
> @node  Widget Minor Mode, Utilities, Widget Browser, Top
> @comment  node-name,  next,  previous,  up
>-@section Widget Minor Mode
>+@chapter Widget Minor Mode
> @cindex widget minor mode
> 
> There is a minor mode for manipulating widgets in major modes that
>@@ -1899,7 +1899,7 @@
> 
> @node  Utilities, Widget Wishlist, Widget Minor Mode, Top
> @comment  node-name,  next,  previous,  up
>-@section Utilities.
>+@chapter Utilities.
> @cindex utility functions for widgets
> 
> @defun widget-prompt-value widget prompt [ value unbound ]
>@@ -1915,7 +1915,7 @@
> 
> @node Widget Wishlist, Widget Internals, Utilities, Top
> @comment  node-name,  next,  previous,  up
>-@section Wishlist
>+@chapter Wishlist
> @cindex todo
> 
> @itemize @bullet
>@@ -1987,7 +1987,7 @@
> @end itemize
> 
> @node Widget Internals, GNU Free Documentation License, Widget Wishlist, Top
>-@section Internals
>+@chapter Internals
> 
> This (very brief!) section provides a few notes on the internal
> structure and implementation of Emacs widgets.  Avoid relying on this
>@@ -1995,7 +1995,7 @@
> To the extent that it actually describes APIs, the information will be
> moved to appropriate sections of the manual in due course.
> 
>-@subsection The @dfn{Widget} and @dfn{Type} Structures
>+@section The @dfn{Widget} and @dfn{Type} Structures
> 
> Widgets and types are currently both implemented as lists.
> 
>diff -Naur xemacs-21.5.33.orig/man/xemacs-faq.texi xemacs-21.5.33/man/xemacs-faq.texi
>--- xemacs-21.5.33.orig/man/xemacs-faq.texi	2013-01-04 17:57:14.000000000 +0100
>+++ xemacs-21.5.33/man/xemacs-faq.texi	2013-03-19 16:27:27.226021480 +0100
>@@ -8848,7 +8848,7 @@
> 
> 
> @node Q11.0.1, Q11.0.2, Bleeding Edge, Bleeding Edge
>-@unnumberedsubsec Where is the most recent XEmacs development code?
>+@unnumberedsec Where is the most recent XEmacs development code?
> 
> The most recent XEmacs @emph{development} code is kept in a Mercurial
> repository, hosted by the Debian project.  The read-only URL, for
>@@ -8871,7 +8871,7 @@
> @xref{Q11.2.1, What is Mercurial?}.
> 
> @node Q11.0.2, Q11.0.3, Q11.0.1, Bleeding Edge
>-@unnumberedsubsec Where is the most recent XEmacs stable code?
>+@unnumberedsec Where is the most recent XEmacs stable code?
> 
> The most recent XEmacs @emph{stable} code is kept in a Mercurial
> repository, hosted by the Debian project.  The read-only URL is
>@@ -8887,7 +8887,7 @@
> 
> 
> @node Q11.0.3, Q11.0.4, Q11.0.2, Bleeding Edge
>-@unnumberedsubsec Where is the most recent XEmacs package code?
>+@unnumberedsec Where is the most recent XEmacs package code?
> 
> The most recent XEmacs @emph{packages} code is kept in a CVS
> repository, hosted by the Debian project.  The read-only @code{CVSROOT},
>@@ -8919,7 +8919,7 @@
> 
> 
> @node Q11.0.4, Q11.0.5, Q11.0.3, Bleeding Edge
>-@unnumberedsubsec Why isn't @var{package} available? and what to do about it.
>+@unnumberedsec Why isn't @var{package} available? and what to do about it.
> 
> If a package isn't available from the Packages repository, probably
> nobody has shown enough interest to add it yet.  (Occasionally, there is
>@@ -8937,7 +8937,7 @@
> 
> 
> @node Q11.0.5, Q11.1.1, Q11.0.4, Bleeding Edge
>-@unnumberedsubsec How do I get commit access?
>+@unnumberedsec How do I get commit access?
> 
> To get commit access to XEmacs code, write to
> @email{xemacs-review@@xemacs.org, the XEmacs Review Board} and request
>@@ -8966,7 +8966,7 @@
> 
> 
> @node Q11.1.1, Q11.2.1, Q11.0.5, Bleeding Edge
>-@unnumberedsubsec How do I keep cool using CVS?
>+@unnumberedsec How do I keep cool using CVS?
> 
> You don't.  CVS is just basically and in detail @emph{un}-cool.
> 
>@@ -8981,7 +8981,7 @@
> 
> 
> @node Q11.2.1, Q11.2.2, Q11.1.1, Bleeding Edge
>-@unnumberedsubsec What is Mercurial?
>+@unnumberedsec What is Mercurial?
> 
> Mercurial is a @dfn{distributed version control system}, or DVCS.  This
> means that versioning information can be easily exchanged between
>@@ -9013,7 +9013,7 @@
> 
> 
> @node Q11.2.2, Q11.2.3, Q11.2.1, Bleeding Edge
>-@unnumberedsubsec Where do I get Mercurial?
>+@unnumberedsec Where do I get Mercurial?
> 
> Most OS distributions (including add-on distributions like
> @uref{http://www.cygwin.com/, Cygwin} and
>@@ -9024,7 +9024,7 @@
> 
> 
> @node Q11.2.3, Q11.2.4, Q11.2.2, Bleeding Edge
>-@unnumberedsubsec Do I really have to waste space on history?
>+@unnumberedsec Do I really have to waste space on history?
> 
> Yes, you do.  It's really not that much, though.  In one of my current
> workspaces, I see
>@@ -9044,7 +9044,7 @@
> 
> 
> @node Q11.2.4, Q11.2.5, Q11.2.3, Bleeding Edge
>-@unnumberedsubsec @code{hg diff} gives bizarre output.
>+@unnumberedsec @code{hg diff} gives bizarre output.
> 
> You may see an unreasonable diff (often large) that doesn't seem to
> reflect your work.
>@@ -9098,7 +9098,7 @@
> result of diffing against the "previous" commit.
> 
> @node Q11.2.5, Q11.2.6, Q11.2.4, Bleeding Edge
>-@unnumberedsubsec How do I recover from a bad commit?  (I already pushed.)
>+@unnumberedsec How do I recover from a bad commit?  (I already pushed.)
> 
> Once upon a time, an XEmacs developer wrote:
> 
>@@ -9270,7 +9270,7 @@
> 
> 
> @node Q11.2.6, Q11.2.7, Q11.2.5, Bleeding Edge
>-@unnumberedsubsec How do I recover from a bad commit?  (I haven't pushed yet.)
>+@unnumberedsec How do I recover from a bad commit?  (I haven't pushed yet.)
> 
> If you hadn't yet pushed the commit you now regret, and realize it
> before doing further commits, you can use @code{hg strip tip}.  Then
>@@ -9287,7 +9287,7 @@
> 
> 
> @node Q11.2.7, , Q11.2.6, Bleeding Edge
>-@unnumberedsubsec Testing patches with Mercurial Queues.
>+@unnumberedsec Testing patches with Mercurial Queues.
> 
> When testing a patch proposed on xemacs-beta or xemacs-patches,
> conflicts or new heads often appear later, when using @code{hg pull -u}.

Actions: View | Diff

Attachments on bug 923365: 712806