erc.texi

input texinfo @c -*-texinfo-*- @c %**start of header @setfilename erc.info @settitle ERC @c %**end of header

@dircategory Emacs @direntry * ERC: (erc). Powerful, modular, and extensible IRC client for Emacs. @end direntry

@syncodeindex fn cp

@copying This manual is for ERC version 5.1.2.

Copyright @copyright{} 2005, 2006 Free Software Foundation, Inc.

@quotation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, Front-Cover texts, or Back-Cover Texts. @end quotation @end copying

@titlepage @title ERC manual @subtitle a full-featured IRC client @subtitle for GNU Emacs and XEmacs

@c The following two commands @c start the copyright page. @page @vskip 0pt plus 1filll @insertcopying @end titlepage

@c So the toc is printed at the start @contents

@ifnottex @node Top, Introduction, (dir), (dir) @comment node-name, next, previous, up @top ERC

@insertcopying @end ifnottex

@menu * Introduction:: What is ERC? * Obtaining ERC:: How to get ERC releases and development
versions. * Installation:: Compiling and installing ERC. * Getting Started:: Quick Start guide to using ERC. * Keystroke Summary:: Keystrokes used in ERC buffers. * Modules:: Available modules for ERC. * Advanced Usage:: Cool ways of using ERC. * Getting Help and Reporting Bugs:: * History:: The history of ERC. * Copying:: The GNU General Public License gives you
permission to redistribute ERC on
certain terms; it also explains that
there is no warranty. * GNU Free Documentation License:: The license for this documentation. * Concept Index:: Search for terms.

@detailmenu
--- The Detailed Node Listing ---

Obtaining ERC

* Releases:: Released versions of ERC. * Development:: Latest unreleased development changes.

@end detailmenu @end menu

@node Introduction, Obtaining ERC, Top, Top @comment node-name, next, previous, up @chapter Introduction

ERC is a powerful, modular, and extensible IRC client for Emacs.

It comes with the following capabilities enabled by default.

@itemize @bullet @item Flood control @item Timestamps @item Join channels automatically @item Buttonize URLs, nicknames, and other text @item Wrap long lines @item Highlight or remove IRC control characters @item Highlight pals, fools, and other keywords @item Detect netsplits @item Complete nicknames and commands in a programmable fashion @item Make displayed lines read-only @item Input history @item Track channel activity in the mode-line

@end itemize

@node Obtaining ERC, Installation, Introduction, Top @comment node-name, next, previous, up @chapter Obtaining ERC

@menu * Releases:: Released versions of ERC. * Development:: Latest unreleased development changes. @end menu

These sections may be skipped if you are using the version of ERC that comes with Emacs.

@node Releases, Development, Obtaining ERC, Obtaining ERC @comment node-name, next, previous, up @section Releases

Choose to install a release if you want to minimize risk.

Errors are corrected in development first. User-visible changes will be announced on the @email{erc-help@@lists.sourceforge.net} mailing list. @pxref{Getting Help and Reporting Bugs}.

@cindex releases, Debian package @cindex Debian package for ERC Debian users can get ERC via apt-get. The @file{erc} package is available in the official Debian repository.

@cindex releases, from source Alternatively, you can download the latest release from @uref{http://sourceforge.net/project/showfiles.php?group_id=30118}.

@node Development, , Releases, Obtaining ERC @comment node-name, next, previous, up @section Development @cindex development

Choose the development version if you want to live on the bleeding edge of ERC development or try out new features before release.

@subsection Using CVS @cindex CVS, using

ERC is primarily developed using a CVS repository on sourceforge.net. To check out a copy of the latest changes, do the following.

@example cvs -d:pserver:anonymous@@cvs.sourceforge.net:/cvsroot/erc login cvs -z3 -d:pserver:anonymous@@cvs.sourceforge.net:/cvsroot/erc co -P erc @end example

@cindex CVS snapshot Alternatively, the latest CVS snapshot may be downloaded in the following forms.

@itemize @bullet @item http://mwolson.org/static/dist/erc-latest.tar.gz @item http://mwolson.org/static/dist/erc-latest.zip @end itemize

@subsection Using the GNU Arch Revision Control System @cindex arch revision control system, using The Arch revision control system allows you to retrieve previous versions and select specific features and bug fixes.

Michael Olson maintains an official Arch branch for ERC which stays current with the CVS repository for ERC. If you would like to contribute to ERC development, and would prefer to use a modern Revision Control System, feel free to make your own branch.

If you are new to Arch, you might find this tutorial helpful: @uref{http://www.mwolson.org/projects/ArchTutorial.html}.

Downloading ERC with Arch and staying up-to-date involves the following steps.

@enumerate @item Install arch

@itemize @bullet @item Debian: @kbd{apt-get install tla}. @item Other distributions: see @uref{ftp://ftp.gnu.org/gnu/gnu-arch/}. @end itemize

@item Register the archive. @example tla register-archive -f http://www.mwolson.org/archives/2006 @end example

@item Download the ERC source code. @example # Download ERC into the @file{erc} directory. tla get mwolson@@gnu.org--2006/erc--cvs--0 erc @end example

@item List upstream changes that are missing from your local copy. Do this whenever you want to see whether new changes have been committed to ERC.

@example # Change to the source directory you are interested in. cd erc/

# Display the summary of changes tla missing --summary @end example

@cindex updating ERC with Arch @item Update to the latest version by replaying missing changes. @example cd erc tla replay @end example

@end enumerate

There are other ways to interact with the ERC archive.

@itemize @item Browse arch repository: @uref{http://www.mwolson.org/archives/} @item Latest development snapshot: @uref{http://www.mwolson.org/static/dist/erc-latest.tar.gz} @end itemize

The latest development snapshot will be kept up-to-date since it is updated at the same time as the Arch repository.

@node Installation, Getting Started, Obtaining ERC, Top @comment node-name, next, previous, up @chapter Installation

ERC may be compiled and installed on your machine.

This section may be skipped if you are using the version of ERC that comes with Emacs.

@subsubheading Compilation

This is an optional step, since Emacs Lisp source code does not necessarily have to be byte-compiled. It will yield a speed increase, though.

A working copy of Emacs or XEmacs is needed in order to compile ERC. By default, the program that is installed with the name @command{emacs} will be used.

If you want to use the @command{xemacs} binary to perform the compilation, you would need to edit @file{Makefile} in the top-level directory as follows. You can put either a full path to an Emacs or XEmacs binary or just the command name, as long as it is in the @env{PATH}.

@example EMACS = xemacs SITEFLAG = -no-site-file @end example

Running @code{make} should compile the ERC source files in the @file{lisp} directory.

@subsubheading Installation

ERC may be installed into your file hierarchy by doing the following.

Edit the @file{Makefile} file so that @env{ELISPDIR} points to where you want the source and compiled ERC files to be installed and @env{INFODIR} indicates where to put the ERC manual. Of course, you will want to edit @env{EMACS} and @env{SITEFLAG} as shown in the Compilation section if you are using XEmacs.

If you are installing ERC on a Debian system, you might want to change the value of @env{INSTALLINFO} as specified in @file{Makefile}.

Run @code{make} as a normal user.

Run @code{make install} as the root user if you have chosen installation locations that require this.

@node Getting Started, Keystroke Summary, Installation, Top @comment node-name, next, previous, up @chapter Getting Started @cindex settings

@c PRE5_2: Mention .ercrc.el

To use ERC, add the directory containing its files to your @code{load-path} variable, in your @file{.emacs} file. Then, load ERC itself along with any extra modules you desire. An example follows.

@lisp (require 'erc)

(require 'erc-spelling) @end lisp

Once this is loaded, the command @kbd{M-x erc-select} will start ERC and prompt for the server to connect to.

@c PRE5_2: Sample session, including: @c - connect to Freenode @c - /join #emacs @c - see messages flying past, point out topic lines, messages, channel @c members @c - identifying your nick with NickServ (most IRC servers have this) @c - talking to the channel @c - open a /query buffer to talk to someone (must identify first in @c FreeNode)

@node Keystroke Summary, Modules, Getting Started, Top @comment node-name, next, previous, up @chapter Keys Used in ERC @cindex keystrokes

This is a summary of keystrokes available in every ERC buffer.

@table @kbd

@item C-a or <home> (`erc-bol') Go to beginning of line or end of prompt.

@item RET (`erc-send-current-line') Send the current line

@item TAB (`erc-complete-word') If at prompt, complete the current word. Otherwise, move to the next link or button.

@item M-TAB (`ispell-complete-word') Complete the given word, using ispell.

@item C-c C-a (`erc-bol') Go to beginning of line or end of prompt.

@item C-c C-b (`erc-iswitchb') Use `iswitchb-read-buffer' to prompt for a ERC buffer to switch to.

@item C-c C-c (`erc-toggle-interpret-controls') Toggle interpretation of control sequences in messages.

@item C-c C-d (`erc-input-action') Interactively input a user action and send it to IRC.

@item C-c C-e (`erc-toggle-ctcp-autoresponse') Toggle automatic CTCP replies (like VERSION and PING).

@item C-c C-f (`erc-toggle-flood-control') Toggle use of flood control on sent messages.

@item C-c TAB (`erc-invite-only-mode') Turn on the invite only mode (+i) for the current channel.

@item C-c C-j (`erc-join-channel') Join channel. If point is at the beginning of a channel name, use that as default.

@item C-c C-k (`erc-go-to-log-matches-buffer') Interactively open an erc-log-matches buffer

@item C-c C-l (`erc-save-buffer-in-logs') Append buffer contents to the log file, if logging is enabled.

@item C-c C-n (`erc-channel-names') Run "/names #channel" in the current channel.

@item C-c C-o (`erc-get-channel-mode-from-keypress') Read a key sequence and call the corresponding channel mode function. After doing C-c C-o type in a channel mode letter.

C-g means quit. RET let's you type more than one mode at a time. If "l" is pressed, `erc-set-channel-limit' gets called. If "k" is pressed, `erc-set-channel-key' gets called. Anything else will be sent to `erc-toggle-channel-mode'.

@item C-c C-p (`erc-part-from-channel') Part from the current channel and prompt for a reason.

@item C-c C-q (`erc-quit-server') Disconnect from current server after prompting for reason.

@item C-c C-r (`erc-remove-text-properties-region') Clears the region (start,end) in object from all colors, etc.

@item C-c C-t (`erc-set-topic') Prompt for a topic for the current channel.

@item C-c C-u (`erc-kill-input') Kill current input line using `erc-bol' followed by `kill-line'.

@end table

@node Modules, Advanced Usage, Keystroke Summary, Top @comment node-name, next, previous, up @chapter Modules @cindex modules

One way to add functionality to ERC is to customize which of its many modules are loaded.

There is a spiffy customize interface, which may be reached by typing @kbd{M-x customize-option erc-modules RET}. Alternatively, set @code{erc-modules} manually and then call @code{erc-update-modules}.

The following is a list of available modules.

@table @code

@cindex modules, autoaway @item autoaway Set away status automatically.

@cindex modules, autojoin @item autojoin Join channels automatically

@cindex modules, bbdb @item bbdb Integrate with the Big Brother Database

@cindex modules, button @item button Buttonize URLs, nicknames, and other text

@cindex modules, fill @item fill Wrap long lines

@cindex modules, irccontrols @item irccontrols Highlight or remove IRC control characters

@cindex modules, log @item log Save buffers in logs

@cindex modules, match @item match Highlight pals, fools, and other keywords

@cindex modules, netsplit @item netsplit Detect netsplits

@cindex modules, noncommands @item noncommands Don't display non-IRC commands after evaluation

@cindex modules, notify @item notify Notify when the online status of certain users changes

@cindex modules, pcomplete @item pcomplete Complete nicknames and commands (programmable)

@cindex modules, readonly @item readonly Make displayed lines read-only

@cindex modules, replace @item replace Replace text in messages

@cindex modules, ring @item ring Enable an input history

@cindex modules, scrolltobottom @item scrolltobottom Scroll to the bottom of the buffer

@cindex modules, services @item services Identify to Nickserv (IRC Services) automatically

@cindex modules, smiley @item smiley Convert smileys to pretty icons

@cindex modules, sound @item sound Play sounds when you receive CTCP SOUND requests

@cindex modules, spell @item spell Check spelling

@cindex modules, stamp @item stamp Add timestamps to messages

@cindex modules, track @item track Track channel activity in the mode-line

@cindex modules, truncate @item truncate Truncate buffers to a certain size

@cindex modules, unmorse @item unmorse Translate morse code in messages

@end table

@c PRE5_2: Document every option of every module in its own subnode

@node Advanced Usage, Getting Help and Reporting Bugs, Modules, Top @comment node-name, next, previous, up @chapter Advanced Usage @cindex advanced topics

Write me.

@c PRE5_2: (Node) Document every ERC option

@c PRE5_2: (Node) Tips and tricks

@c PRE5_2: (Node) Sample configs

@node Getting Help and Reporting Bugs, History, Advanced Usage, Top @comment node-name, next, previous, up @chapter Getting Help and Reporting Bugs @cindex help, getting @cindex bugs, reporting

After you have read this guide, if you still have questions about ERC, or if you have bugs to report, there are several places you can go.

@itemize @bullet

@item @uref{http://www.emacswiki.org/cgi-bin/wiki/EmacsIRCClient} is the emacswiki.org page for ERC. Anyone may add tips, hints, or bug descriptions to it.

@item You can join the mailing list at @email{erc-help@@lists.sourceforge.net} using the subscription form at @uref{http://lists.sourceforge.net/lists/listinfo/erc-help}.

This mailing list is also available via Gmane (@url{http://gmane.org/}). The group is called @samp{gmane.emacs.erc.general}. This provides additional methods for accessing the mailing list, adding content to it, and searching it.

@item You can visit the IRC Freenode channel @samp{#emacs}. Many of the contributors are frequently around and willing to answer your questions.

@end itemize

@node History, Copying, Getting Help and Reporting Bugs, Top @comment node-name, next, previous, up @chapter History @cindex history, of ERC

ERC was originally written by Alexander L. Belikoff @email{abel@@bfr.co.il} and Sergey Berezin @email{sergey.berezin@@cs.cmu.edu}. They stopped development around december 1999. Their last released version was ERC 2.0.

P.S.: If one of the original developers of ERC reads this, we'd like to receive additional information for this file and hear comments in general.

@itemize @item 2001

In June 2001, Mario Lang @email{mlang@@delysid.org} and Alex Schroeder @email{alex@@gnu.org} took over development and created a ERC Project at sourceforge.net.

In reaction to a mail about the new erc development, Sergey Berezin said, "First of all, I'm glad that my version of ERC is being used out there. The thing is, I do not have free time and enough incentive anymore to work on ERC, so I would be happy if you guys take over the project entirely."

So we happily hacked away on ERC, and soon after (september 2001) released the next "stable" version, 2.1.

Most of the development of the new ERC happend on #emacs on irc.openprojects.net. Over time, many people contributed code, ideas, bugfixes. And not to forget alot of alpha/beta/gamma testing.

See the @file{CREDITS} file for a list of contributors.

@item 2003

ERC 3.0 is released.

@item 2004

ERC 4.0 is released.

@item 2005

ERC 5.0 is released. Michael Olson @email{mwolson@@gnu.org} becomes the release manager and eventually the maintainer.

After some discussion between him and the Emacs developers, it is decided to include ERC in Emacs.

@item 2006

ERC 5.1 is released. It is subsequently included in Emacs 22.

@end itemize

@node Copying, GNU Free Documentation License, History, Top @comment node-name, next, previous, up @appendix COPYING @center Version 2, June 1991 @cindex GPL @cindex GNU General Public License

@display Copyright @copyright{} 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @end display

@appendixsec Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software---to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

@iftex @appendixsec TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end iftex @ifinfo @center TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION @end ifinfo

@enumerate 0 @item This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The ``Program'', below, refers to any such program or work, and a ``work based on the Program'' means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term ``modification''.) Each licensee is addressed as ``you''.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

@item You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

@item You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

@enumerate a @item You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

@item You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

@item If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) @end enumerate

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

@item You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

@enumerate a @item Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

@item Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

@item Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) @end enumerate

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

@item You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

@item You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

@item Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

@item If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

@item If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

@item The Free Software Foundation may publish revised and/or new versions of the General Public 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.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and ``any later version'', you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

@item If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

@iftex @heading NO WARRANTY @end iftex @ifinfo @center NO WARRANTY @end ifinfo

@item BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

@item IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. @end enumerate

@iftex @heading END OF TERMS AND CONDITIONS @end iftex @ifinfo @center END OF TERMS AND CONDITIONS @end ifinfo

@page @appendixsec Appendix: How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the ``copyright'' line and a pointer to where the full notice is found.

@smallexample @var{one line to give the program's name and a brief idea of what it does.} Copyright (C) @var{yyyy} @var{name of author}

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. @end smallexample

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

@smallexample Gnomovision version 69, Copyright (C) 19@var{yy} @var{name of author} Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. @end smallexample

The hypothetical commands @samp{show w} and @samp{show c} should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than @samp{show w} and @samp{show c}; they could even be mouse-clicks or menu items---whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a ``copyright disclaimer'' for the program, if necessary. Here is a sample; alter the names:

@example Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.

@var{signature of Ty Coon}, 1 April 1989 Ty Coon, President of Vice @end example

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

@node GNU Free Documentation License, Concept Index, Copying, Top @comment node-name, next, previous, up @appendix GNU Free Documentation License @center Version 1.2, November 2002

@display Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @end display @sp 1 @enumerate 0 @item PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document ``free'' in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of ``copyleft'', which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a 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 instruction or reference.

@sp 1 @item 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 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.

A ``Modified Version'' of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A ``Secondary Section'' is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position 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.

The ``Cover Texts'' are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

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.''

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.

The ``Title Page'' means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, ``Title Page'' means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

A section ``Entitled XYZ'' means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as ``Acknowledgements'', ``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title'' of such a section when you modify the Document means that it remains a section ``Entitled XYZ'' according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. @sp 1 @item VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You 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.

You may also lend copies, under the same conditions stated above, and you may publicly display copies. @sp 1 @item COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all 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.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto 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.

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. @sp 1 @item 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:

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.@* B. List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.@* C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.@* D. Preserve all the copyright notices of the Document.@* E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.@* F. Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.@* G. Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.@* H. Include an unaltered copy of this License.@* 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.@* 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.@* 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 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.@* M. Delete any section Entitled ``Endorsements.'' Such a section
may not be included in the Modified Version.@* N. Do not retitle any existing section to be Entitled ``Endorsements''
or to conflict in title with any Invariant Section.@* O. Preserve any Warranty Disclaimers.@* @sp 1 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.

You may add a section Entitled ``Endorsements'', provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative 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.

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 assert or imply endorsement of any Modified Version. @sp 1 @item COMBINING DOCUMENTS

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, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled ``History'' in the various original documents, forming one section Entitled ``History''; likewise combine any sections Entitled ``Acknowledgements'', and any sections Entitled ``Dedications.'' You must delete all sections Entitled ``Endorsements.'' @sp 1 @item COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other 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.

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. @sp 1 @item 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 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 License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. @sp 1 @item TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled ``Acknowledgements'', ``Dedications'', or ``History'', the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. @sp 1 @item TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. @sp 1 @item 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/.

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.

@end enumerate

@unnumberedsec ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

@smallexample @group Copyright (C) @var{year} @var{your name}. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''. @end group @end smallexample

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the ``with...Texts.'' line with this:

@smallexample @group with the Invariant Sections being @var{list their titles}, with the Front-Cover Texts being @var{list}, and with the Back-Cover Texts being @var{list}. @end group @end smallexample

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the 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.

@node Concept Index, , GNU Free Documentation License, Top @comment node-name, next, previous, up @unnumbered Index

@printindex cp

@bye

@ignore
arch-tag: cf9cfaff-fc12-4297-ad15-ec2493002b1e @end ignore