-This is ../gpr-mode.info, produced by makeinfo version 4.13 from
-../gpr-mode.texi.
+This is gpr-mode.info, produced by makeinfo version 5.2 from
+gpr-mode.texi.
-Copyright (C) 2013 Free Software Foundation, Inc.
+Copyright (C) 2013 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
(a) The FSF's Back-Cover Text is: "You have the freedom to copy and
modify this GNU manual. Buying copies from the FSF supports it in
developing GNU and promoting software freedom."
-
INFO-DIR-SECTION Emacs editing modes
START-INFO-DIR-ENTRY
* gpr mode: (gpr-mode). Emacs mode for editing and navigating gpr files (gnat project files).
\1f
File: gpr-mode.info, Node: Top, Next: Overview, Prev: (dir), Up: (dir)
- Copyright (C) 2013 Free Software Foundation, Inc.
+Copyright (C) 2013 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
1 Overview
**********
-gpr files are the project files used by the GNAT compiler and
-associated tools. They describe search paths, compiler options, etc.
+gpr files are the project files used by the GNAT compiler and associated
+tools. They describe search paths, compiler options, etc.
*Note GNAT Project Manager: (gnat_ugn)GNAT Project Manager, for
general information on gpr files.
The Emacs mode for gpr files helps the user in reading existing code
and facilitates writing new code.
- When you open a file with a file extension of `.gpr', Emacs will
+ When you open a file with a file extension of '.gpr', Emacs will
automatically load and activate gpr mode.
\1f
**************
gpr mode is distributed in the Gnu ELPA package archive, bundled with
-Ada mode; it can be installed via `M-x list-packages' (*note Packages:
-(emacs)Packages.).
+Ada mode; it can be installed via 'M-x list-packages' (*note
+(emacs)Packages::).
gpr mode is also available as a separate distribution bundled with
Ada mode, from the Emacs Ada mode website
-`http://stephe-leake.org/emacs/ada-mode/emacs-ada-mode.html'. The
+<http://stephe-leake.org/emacs/ada-mode/emacs-ada-mode.html>. The
separate distribution may be more recent.
- For installing the separate distribution, see the `README' file in
+ For installing the separate distribution, see the 'README' file in
the distribution.
gpr mode does not have a separate version; it uses the Ada mode
-version number. To see what version of Ada mode you have installed, do
-`M-x ada-mode-version'.
+version number. To see what version of Ada mode you have installed, do
+'M-x ada-mode-version'.
\1f
File: gpr-mode.info, Node: Customization, Next: Moving Through Gpr Code, Prev: Installation, Up: Top
***************
gpr mode uses the Ada mode indentation variables; they can be set via
-the menu `Ada | Customize' from an Ada mode buffer. Click on the
-`Help' button there for help on using customize.
+the menu 'Ada | Customize' from an Ada mode buffer. Click on the 'Help'
+button there for help on using customize.
To modify a specific variable, you can directly call the function
-`customize-variable'; just type `M-x customize-variable <RET>
+'customize-variable'; just type 'M-x customize-variable <RET>
VARIABLE-NAME <RET>').
Alternately, you can specify variable settings in the Emacs
-configuration file, `~/.emacs'. This file is coded in Emacs lisp, and
+configuration file, '~/.emacs'. This file is coded in Emacs lisp, and
the syntax to set a variable is the following:
(setq variable-name value)
Some general Emacs settings that are useful for gpr files:
-`delete-trailing-whitespace'
+'delete-trailing-whitespace'
Deletes space, tab at end of line and blank lines at end of buffer.
-
-`untabify'
+'untabify'
Deletes tab characters that have crept into the file.
-
-`indent-tabs-mode'
+'indent-tabs-mode'
Don't insert tab characters when indenting.
-
-`hippie-expand'
- Bind `hippie-expand' to a key; it expands the word before point,
+'hippie-expand'
+ Bind 'hippie-expand' to a key; it expands the word before point,
using words from current buffer, other buffers, file names, etc;
- see `hippie-expand-try-functions-list'. You can also add
- `skeleton-hippie-try' to that list (*note Statement skeletons::).
+ see 'hippie-expand-try-functions-list'. You can also add
+ 'skeleton-hippie-try' to that list (*note Statement skeletons::).
- The above can all be set by the following code in your `~/.emacs'.
-Note that some are functions are added to `before-save-hook'; they run
+ The above can all be set by the following code in your '~/.emacs'.
+Note that some are functions are added to 'before-save-hook'; they run
just before a buffer is written to disk.
(setq-default indent-tabs-mode nil)
(require 'gpr-mode)
4 Moving Through Gpr Code
*************************
-These commands navigate through gpr code. All these functions are
+These commands navigate through gpr code. All these functions are
available through the gpr menu and keybindings.
-`C-c C-o'
- If point is on a `with' clause, position point on the
- corresponding package declaration.
+'C-c C-o'
+ If point is on a 'with' clause, position point on the corresponding
+ package declaration.
-`C-u SPACE'
+'C-u SPACE'
Jump back to the previous location.
-
\1f
File: gpr-mode.info, Node: Identifier completion, Next: Indentation, Prev: Moving Through Gpr Code, Up: Top
5 Identifier completion
***********************
-Emacs provides a general way of completing identifiers: `M-/' (bound to
-`dabbrev-expand'). This is an easy way to type faster: you just have to
+Emacs provides a general way of completing identifiers: 'M-/' (bound to
+'dabbrev-expand'). This is an easy way to type faster: you just have to
type the first few letters of an identifier, and then loop through all
the possible completions.
- `M-/' works by parsing all open gpr files for possible completions.
+ 'M-/' works by parsing all open gpr files for possible completions.
- For instance, if the words `my_identifier' and `my_subprogram' are
-the only words starting with `my' in any of the open gpr files, then
-you will have this scenario:
+ For instance, if the words 'my_identifier' and 'my_subprogram' are
+the only words starting with 'my' in any of the open gpr files, then you
+will have this scenario:
You type: myM-/
- Emacs inserts: `my_identifier'
- If you press M-/ once again, Emacs replaces `my_identifier' with
- `my_subprogram'.
- Pressing M-/ once more will bring you back to `my_identifier'.
+ Emacs inserts: 'my_identifier'
+ If you press M-/ once again, Emacs replaces 'my_identifier' with
+ 'my_subprogram'.
+ Pressing M-/ once more will bring you back to 'my_identifier'.
This is a very fast way to do completion, and the casing of words
will also be respected.
6 Indentation
*************
-gpr mode comes with a full set of rules for automatic indentation. You
+gpr mode comes with a full set of rules for automatic indentation. You
can also configure the indentation, via the following variables:
-`ada-indent' (default value: 3)
+'ada-indent' (default value: 3)
Number of columns for default indentation.
-`ada-indent-broken' (default value: 2)
+'ada-indent-broken' (default value: 2)
Number of columns to indent the continuation of a broken line.
-`ada-indent-when' (default value: 3)
- Indentation for `when' relative to `exception', `case', or `or' in
- `select'.
-
-`ada-indent-with' (default value: ada-indent-broken)
- Indentation for the lines in a `with' context clause.
+'ada-indent-when' (default value: 3)
+ Indentation for 'when' relative to 'exception', 'case', or 'or' in
+ 'select'.
+'ada-indent-with' (default value: ada-indent-broken)
+ Indentation for the lines in a 'with' context clause.
The following keys indent portions of the text:
-`RET'
+
+'RET'
Insert and indent a new line.
-`TAB'
+'TAB'
Indent the current line, or the current region.
-`C-c TAB'
+'C-c TAB'
Indent the current declaration.
-
The indentation algorithm relies on a grammar parser to identify the
-syntactic role for keywords and other words in the code. If the code is
+syntactic role for keywords and other words in the code. If the code is
accepted by the parser, the indentation is done according to the rules
in the indentation engine.
If the code is not accepted (because it is partially complete during
editing), the indentation engine falls back to the trivial algorithm of
-indenting each new line the same as the previous line. Once enough new
+indenting each new line the same as the previous line. Once enough new
text has been entered to make the code acceptable to the parser, the
declaration is properly indented.
("../../1553/test",
"../../system/test");
- when you type `RET (', `(' is indented to the same column as `for',
-because the parser does not find `);'. Then when you type the final `;'
-followed by <TAB>, all three lines are indented, putting `(' where it
+ when you type 'RET (', '(' is indented to the same column as 'for',
+because the parser does not find ');'. Then when you type the final ';'
+followed by <TAB>, all three lines are indented, putting '(' where it
belongs.
To be more user friendly, the parser accepts a superset of the gpr
-grammer. For example, the parser accepts this code for a `case'
+grammer. For example, the parser accepts this code for a 'case'
statement:
case is
Statement skeletons::.
In rare cases, the parser gets confused; it can be reset by invoking
-menu <gpr | Misc | Reset parser>. Please report such cases as a bug.
+menu <gpr | Misc | Reset parser>. Please report such cases as a bug.
\1f
File: gpr-mode.info, Node: Statement skeletons, Next: GNU Free Documentation License, Prev: Indentation, Up: Top
7 Statement skeletons
*********************
-`C-c C-e' expands the previous one or two words into a statment
-skeleton. For example, `c a s e C-c C-e' expands to:
+'C-c C-e' expands the previous one or two words into a statment
+skeleton. For example, 'c a s e C-c C-e' expands to:
case is
when =>
All skeleton expansions are accepted by the indentation parser, so
this is a convenient way to insert statements with correct indentation.
- For named packages, the name is taken from the word before point,
-and the package keyword from the word before that:
+ For named packages, the name is taken from the word before point, and
+the package keyword from the word before that:
package A_Package
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008, 2009 Free Software Foundation, Inc.
- `http://fsf.org/'
+ <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
- of subject matter or whether it is published as a printed book.
- We recommend this License principally for works whose purpose is
+ of subject matter or whether it is published as a printed book. We
+ recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
- that contains a notice placed by the copyright holder saying it
- can be distributed under the terms of this License. Such a notice
+ that contains a notice placed by the copyright holder saying it can
+ be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
"Document", below, refers to any such manual or work. Any member
- of the public is a licensee, and is addressed as "you". You
- accept the license if you copy, modify or distribute the work in a
- way requiring permission under copyright law.
+ of the public is a licensee, and is addressed as "you". You accept
+ the license if you copy, modify or distribute the work in a way
+ requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
regarding them.
The "Invariant Sections" are certain Secondary Sections whose
- titles are designated, as being those of Invariant Sections, in
- the notice that says that the Document is released under this
- License. If a section does not fit the above definition of
- Secondary then it is not allowed to be designated as Invariant.
- The Document may contain zero Invariant Sections. If the Document
- does not identify any Invariant Sections then there are none.
+ titles are designated, as being those of Invariant Sections, in the
+ notice that says that the Document is released under this License.
+ If a section does not fit the above definition of Secondary then it
+ is not allowed to be designated as Invariant. The Document may
+ contain zero Invariant Sections. If the Document does not identify
+ any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
- straightforwardly with generic text editors or (for images
- composed of pixels) generic paint programs or (for drawings) some
- widely available drawing editor, and that is suitable for input to
- text formatters or for automatic translation to a variety of
- formats suitable for input to text formatters. A copy made in an
- otherwise Transparent file format whose markup, or absence of
- markup, has been arranged to thwart or discourage subsequent
- modification by readers is not Transparent. An image format is
- not Transparent if used for any substantial amount of text. A
- copy that is not "Transparent" is called "Opaque".
+ straightforwardly with generic text editors or (for images composed
+ of pixels) generic paint programs or (for drawings) some widely
+ available drawing editor, and that is suitable for input to text
+ formatters or for automatic translation to a variety of formats
+ suitable for input to text formatters. A copy made in an otherwise
+ Transparent file format whose markup, or absence of markup, has
+ been arranged to thwart or discourage subsequent modification by
+ readers is not Transparent. An image format is not Transparent if
+ used for any substantial amount of text. A copy that is not
+ "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
- SGML or XML using a publicly available DTD, and
- standard-conforming simple HTML, PostScript or PDF designed for
- human modification. Examples of transparent image formats include
- PNG, XCF and JPG. Opaque formats include proprietary formats that
- can be read and edited only by proprietary word processors, SGML or
- XML for which the DTD and/or processing tools are not generally
- available, and the machine-generated HTML, PostScript or PDF
- produced by some word processors for output purposes only.
+ SGML or XML using a publicly available DTD, and standard-conforming
+ simple HTML, PostScript or PDF designed for human modification.
+ Examples of transparent image formats include PNG, XCF and JPG.
+ Opaque formats include proprietary formats that can be read and
+ edited only by proprietary word processors, SGML or XML for which
+ the DTD and/or processing tools are not generally available, and
+ the machine-generated HTML, PostScript or PDF produced by some word
+ processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
- distribute a large enough number of copies you must also follow
- the conditions in section 3.
+ distribute a large enough number of copies you must also follow the
+ conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
- front cover must present the full title with all words of the
- title equally prominent and visible. You may add other material
- on the covers in addition. Copying with changes limited to the
- covers, as long as they preserve the title of the Document and
- satisfy these conditions, can be treated as verbatim copying in
- other respects.
+ front cover must present the full title with all words of the title
+ equally prominent and visible. You may add other material on the
+ covers in addition. Copying with changes limited to the covers, as
+ long as they preserve the title of the Document and satisfy these
+ conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
adjacent pages.
If you publish or distribute Opaque copies of the Document
- numbering more than 100, you must either include a
- machine-readable Transparent copy along with each Opaque copy, or
- state in or with each Opaque copy a computer-network location from
- which the general network-using public has access to download
- using public-standard network protocols a complete Transparent
- copy of the Document, free of added material. If you use the
- latter option, you must take reasonably prudent steps, when you
- begin distribution of Opaque copies in quantity, to ensure that
- this Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you
- distribute an Opaque copy (directly or through your agents or
- retailers) of that edition to the public.
+ numbering more than 100, you must either include a machine-readable
+ Transparent copy along with each Opaque copy, or state in or with
+ each Opaque copy a computer-network location from which the general
+ network-using public has access to download using public-standard
+ network protocols a complete Transparent copy of the Document, free
+ of added material. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly or
+ through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
- the Document well before redistributing any large number of
- copies, to give them a chance to provide you with an updated
- version of the Document.
+ the Document well before redistributing any large number of copies,
+ to give them a chance to provide you with an updated version of the
+ Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
- release the Modified Version under precisely this License, with
- the Modified Version filling the role of the Document, thus
- licensing distribution and modification of the Modified Version to
- whoever possesses a copy of it. In addition, you must do these
- things in the Modified Version:
+ release the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus licensing
+ distribution and modification of the Modified Version to whoever
+ possesses a copy of it. In addition, you must do these things in
+ the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
- distinct from that of the Document, and from those of
- previous versions (which should, if there were any, be listed
- in the History section of the Document). You may use the
- same title as a previous version if the original publisher of
- that version gives permission.
+ distinct from that of the Document, and from those of previous
+ versions (which should, if there were any, be listed in the
+ History section of the Document). You may use the same title
+ as a previous version if the original publisher of that
+ version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
- authors, and publisher of the Modified Version as given on
- the Title Page. If there is no section Entitled "History" in
- the Document, create one stating the title, year, authors,
- and publisher of the Document as given on its Title Page,
- then add an item describing the Modified Version as stated in
- the previous sentence.
+ authors, and publisher of the Modified Version as given on the
+ Title Page. If there is no section Entitled "History" in the
+ Document, create one stating the title, year, authors, and
+ publisher of the Document as given on its Title Page, then add
+ an item describing the Modified Version as stated in the
+ previous sentence.
J. Preserve the network location, if any, given in the Document
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
- previous versions it was based on. These may be placed in
- the "History" section. You may omit a network location for a
- work that was published at least four years before the
- Document itself, or if the original publisher of the version
- it refers to gives permission.
+ previous versions it was based on. These may be placed in the
+ "History" section. You may omit a network location for a work
+ that was published at least four years before the Document
+ itself, or if the original publisher of the version it refers
+ to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the
- section all the substance and tone of each of the contributor
+ Preserve the Title of the section, and preserve in the section
+ all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section
- titles.
+ L. Preserve all the Invariant Sections of the Document, unaltered
+ in their text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
- material copied from the Document, you may at your option
- designate some or all of these sections as invariant. To do this,
- add their titles to the list of Invariant Sections in the Modified
- Version's license notice. These titles must be distinct from any
- other section titles.
+ material copied from the Document, you may at your option designate
+ some or all of these sections as invariant. To do this, add their
+ titles to the list of Invariant Sections in the Modified Version's
+ license notice. These titles must be distinct from any other
+ section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
- and a passage of up to 25 words as a Back-Cover Text, to the end
- of the list of Cover Texts in the Modified Version. Only one
- passage of Front-Cover Text and one of Back-Cover Text may be
- added by (or through arrangements made by) any one entity. If the
- Document already includes a cover text for the same cover,
- previously added by you or by arrangement made by the same entity
- you are acting on behalf of, you may not add another; but you may
- replace the old one, on explicit permission from the previous
- publisher that added the old one.
+ and a passage of up to 25 words as a Back-Cover Text, to the end of
+ the list of Cover Texts in the Modified Version. Only one passage
+ of Front-Cover Text and one of Back-Cover Text may be added by (or
+ through arrangements made by) any one entity. If the Document
+ already includes a cover text for the same cover, previously added
+ by you or by arrangement made by the same entity you are acting on
+ behalf of, you may not add another; but you may replace the old
+ one, on explicit permission from the previous publisher that added
+ the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
- modified versions, provided that you include in the combination
- all of the Invariant Sections of all of the original documents,
+ modified versions, provided that you include in the combination all
+ of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
- rules of this License for verbatim copying of each of the
- documents in all other respects.
+ rules of this License for verbatim copying of each of the documents
+ in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
- a copy of this License into the extracted document, and follow
- this License in all other respects regarding verbatim copying of
- that document.
+ a copy of this License into the extracted document, and follow this
+ License in all other respects regarding verbatim copying of that
+ document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
- separate and independent documents or works, in or on a volume of
- a storage or distribution medium, is called an "aggregate" if the
+ separate and independent documents or works, in or on a volume of a
+ storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
- provisionally, unless and until the copyright holder explicitly
- and finally terminates your license, and (b) permanently, if the
+ provisionally, unless and until the copyright holder explicitly and
+ finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
after your receipt of the notice.
Termination of your rights under this section does not terminate
- the licenses of parties who have received copies or rights from
- you under this License. If your rights have been terminated and
- not permanently reinstated, receipt of a copy of some or all of
- the same material does not give you any rights to use it.
+ the licenses of parties who have received copies or rights from you
+ under this License. If your rights have been terminated and not
+ permanently reinstated, receipt of a copy of some or all of the
+ same material does not give you any rights to use it.
- 10. FUTURE REVISIONS OF THIS LICENSE
+ 10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
- `http://www.gnu.org/copyleft/'.
+ <http://www.gnu.org/copyleft/>.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
- published (not as a draft) by the Free Software Foundation. If
- the Document does not specify a version number of this License,
- you may choose any version ever published (not as a draft) by the
- Free Software Foundation. If the Document specifies that a proxy
- can decide which future versions of this License can be used, that
+ published (not as a draft) by the Free Software Foundation. If the
+ Document does not specify a version number of this License, you may
+ choose any version ever published (not as a draft) by the Free
+ Software Foundation. If the Document specifies that a proxy can
+ decide which future versions of this License can be used, that
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
- 11. RELICENSING
+ 11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
-
ADDENDUM: How to use this License for your documents
====================================================
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
situation.
If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
\1f
File: gpr-mode.info, Node: Index, Prev: GNU Free Documentation License, Up: Top
\1f
Tag Table:
-Node: Top\7f969
-Node: Overview\7f1952
-Node: Installation\7f2510
-Node: Customization\7f3268
-Node: Moving Through Gpr Code\7f5191
-Node: Identifier completion\7f5641
-Node: Indentation\7f6602
-Node: Statement skeletons\7f8978
-Node: GNU Free Documentation License\7f9733
-Node: Index\7f34914
+Node: Top\7f960
+Node: Overview\7f1939
+Node: Installation\7f2498
+Node: Customization\7f3249
+Node: Moving Through Gpr Code\7f5171
+Node: Identifier completion\7f5621
+Node: Indentation\7f6583
+Node: Statement skeletons\7f8913
+Node: GNU Free Documentation License\7f9669
+Node: Index\7f34831
\1f
End Tag Table