Man Pages

erc - phpMan erc - phpMan

Command: man perldoc info search(apropos)  


File: erc,  Node: Top,  Next: Introduction,  Prev: (dir),  Up: (dir)

ERC
***

This manual is for ERC version 5.3.

   Copyright (C) 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
Inc.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.3 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover texts
     being "A GNU Manual," and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     "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."

     All Emacs Lisp code contained in this document may be used,
     distributed, and modified without restriction.

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

 --- The Detailed Node Listing ---

Obtaining ERC

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

Getting Started

* Sample Session::              Example of connecting to the #emacs channel
* Special Features::            Differences from standalone IRC clients

Advanced Usage

* Connecting::                  Ways of connecting to an IRC server.
* Sample Configuration::        An example configuration file.
* Options::                     Options that are available for ERC.

File: erc,  Node: Introduction,  Next: Obtaining ERC,  Prev: Top,  Up: Top

1 Introduction
**************

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

   It comes with the following capabilities enabled by default.

   * Flood control

   * Timestamps

   * Join channels automatically

   * Buttonize URLs, nicknames, and other text

   * Wrap long lines

   * Highlight or remove IRC control characters

   * Highlight pals, fools, and other keywords

   * Detect netsplits

   * Complete nicknames and commands in a programmable fashion

   * Make displayed lines read-only

   * Input history

   * Track channel activity in the mode-line


File: erc,  Node: Obtaining ERC,  Next: Installation,  Prev: Introduction,  Up: Top

2 Obtaining ERC
***************

* Menu:

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

   Note that some ERC files are not included with Emacs due to
copyright or dependency issues.  If desired, they may be found at the
following locations, or from your local GNU mirror.

   * `http://ftp.gnu.org/gnu/erc/erc-5.3-extras.tar.gz'

   * `http://ftp.gnu.org/gnu/erc/erc-5.3-extras.zip'

   The rest of this chapter may be skipped if you are using the version
of ERC that comes with Emacs.

File: erc,  Node: Releases,  Next: Development,  Prev: Obtaining ERC,  Up: Obtaining ERC

2.1 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 <erc-discussATgnu.org> mailing list.  *note
Getting Help and Reporting Bugs::.

   Debian users can get ERC via apt-get.  The `erc' package is
available in the official Debian repository.

   Alternatively, you can download the latest release from
`http://ftp.gnu.org/gnu/erc', or your local GNU mirror.

File: erc,  Node: Development,  Prev: Releases,  Up: Obtaining ERC

2.2 Development
===============

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

   The git version control system allows you to keep up-to-date with the
latest changes to the development version of ERC.  It also allows you
to contribute changes (via commits, if you are have developer access to
the repository, or via patches, otherwise).  If you would like to
contribute to ERC development, it is highly recommended that you use
git.

   If you are new to git, you might find this tutorial helpful:
`http://www.kernel.org/pub/software/scm/git/docs/tutorial.html'.

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

  1. Install git.

        * Debian and Ubuntu: `apt-get install git-core'.

        * Windows: `http://git.or.cz/gitwiki/WindowsInstall'.

        * Other operating systems: download, compile, and install the
          source from `http://www.kernel.org/pub/software/scm/git/', or
          find a git package for your operating system.

  2. Download the ERC development branch.

     If you have developer access to ERC, do:

          git clone ssh://loginnameATgit.org/srv/git/erc.git

     otherwise, do:

          git clone git://git.sv.gnu.org/erc.git

     If you are behind a restrictive firewall, and do not have developer
     access, then do the following instead:

          git clone http://git.sv.gnu.org/r/erc.git

  3. 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.  If you wish, you may skip this step and proceed
     directly to the "update" step.

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

          # Fetch new changes from the repository, but don't apply them yet
          git fetch origin

          # Display log messages for the new changes
          git log HEAD..origin

     "origin" is git's name for the location where you originally got
     ERC from.  You can change this location at any time by editing the
     `.git/config' file in the directory where the ERC source was
     placed.

  4. Update to the latest version by pulling in any missing changes.

          cd erc
          git pull origin

     git will show how many files changed, and will provide a visual
     display for how many lines were changed in each file.


   There are other ways to interact with the ERC repository.

   * Browse git repo: `http://git.sv.gnu.org/gitweb/?p=erc.git'

   * Latest development snapshot:
     `http://mwolson.org/static/dist/erc-latest.tar.gz'

   * Latest development snapshot (zip file):
     `http://mwolson.org/static/dist/erc-latest.zip'

   The latest development snapshot can lag behind the git repo by as
much as 20 minutes, but never more than that.

   For further information on committing changes to ERC and performing
development, please consult
`http://emacswiki.org/cgi-bin/wiki/ErcDevelopment'.

File: erc,  Node: Installation,  Next: Getting Started,  Prev: Obtaining ERC,  Up: Top

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

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 `emacs' will be
used.

   If you want to use the `xemacs' binary to perform the compilation,
you would need to edit `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 `PATH'.

     EMACS    = xemacs
     SITEFLAG = -no-site-file

   Running `make' should compile the ERC source files in the `lisp'
directory.

Installation
............

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

   Edit the `Makefile' file so that `ELISPDIR' points to where you want
the source and compiled ERC files to be installed and `INFODIR'
indicates where to put the ERC manual.  Of course, you will want to
edit `EMACS' and `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 `INSTALLINFO' as specified in `Makefile'.

   Run `make' as a normal user.

   Run `make install' as the root user if you have chosen installation
locations that require this.

File: erc,  Node: Getting Started,  Next: Keystroke Summary,  Prev: Installation,  Up: Top

4 Getting Started
*****************

To use ERC, add the directory containing its files to your `load-path'
variable, in your `.emacs' file.  Then, load ERC itself.  An example
follows.

     (require 'erc)

   Once ERC is loaded, the command `M-x erc' will start ERC and prompt
for the server to connect to.

   If you want to place ERC settings in their own file, you can place
them in `~/.emacs.d/.ercrc.el', creating it if necessary.

   If you would rather use the Customize interface to change how ERC
works, do `M-x customize-group RET erc RET'.  In particular, ERC comes
with lots of modules that may be enabled or disabled; to select which
ones you want, do `M-x customize-variable RET erc-modules RET'.

* Menu:

* Sample Session::              Example of connecting to the #emacs channel
* Special Features::            Differences from standalone IRC clients

File: erc,  Node: Sample Session,  Next: Special Features,  Prev: Getting Started,  Up: Getting Started

4.1 Sample Session
==================

This is an example ERC session which shows how to connect to the #emacs
channel on Freenode.  Another IRC channel on Freenode that may be of
interest is #erc, which is a channel where ERC users and developers hang
out.

   * Connect to Freenode

     Run `M-x erc'.  Use "irc.freenode.net" as the IRC server, "6667"
     as the port, and choose a nickname.

   * Get used to the interface

     Switch to the "irc.freenode.net:6667" buffer, if you're not already
     there.  You will see first some messages about checking for ident,
     and then a bunch of other messages that describe the current IRC
     server.

   * Join the #emacs channel

     In that buffer, type "/join SPC #emacs" and hit `RET'.  Depending
     on how you've set up ERC, either a new buffer for "#emacs" will be
     displayed, or a new buffer called "#emacs" will be created in the
     background.  If the latter, switch to the "#emacs" buffer.  You
     will see the channel topic and a list of the people who are
     currently on the channel.

   * Register your nickname with Freenode

     If you would like to be able to talk with people privately on the
     Freenode network, you will have to "register" your nickname.  To do
     so, switch to the "irc.freenode.net:6667" buffer and type "/msg
     NickServ register <password>", replacing "<password>" with your
     desired password.  It should tell you that the operation was
     successful.

   * Talk to people in the channel

     If you switch back to the "#emacs" buffer, you can type a message,
     and everyone on the channel will see it.

   * Open a query buffer to talk to someone

     If you want to talk with someone in private (this should usually
     not be done for technical help, only for personal questions), type
     "/query <nick>", replacing "<nick>" with the nickname of the
     person you would like to talk to.  Depending on how ERC is set up,
     you will either see a new buffer with the name of the person, or
     such a buffer will be created in the background and you will have
     to switch to it.  Begin typing messages, and you will be able to
     have a conversation.

     Note that if the other person is not registered, you will not be
     able to talk with them.


File: erc,  Node: Special Features,  Prev: Sample Session,  Up: Getting Started

4.2 Special Features
====================

ERC has some features that distinguish it from some IRC clients.

   * multiple channels and multiple servers

     Every channel is put in a separate buffer.  Several IRC servers
     may be connected to at the same time.

   * private message separation

     Private conversations are treated as channels, and are put into
     separate buffers in Emacs.  We call these "query buffers".

   * highlighting

     Some occurrences of words can be highlighted, which makes it
     easier to track different kinds of conversations.

   * notification

     ERC can notify you that certain users are online.

   * channel tracking

     Channels can be hidden and conversation continue in the
     background.  You are notified when something is said in such a
     channel that is not currently visible.  This makes it easy to get
     Real Work done while still maintaining an IRC presence.

   * nick completion

     ERC can complete words upon hitting `TAB', which eases the writing
     of nicknames in messages.

   * history

     Past actions are kept in history rings for future use.  To
     navigate a history ring, hit `M-p' to go backwards and `M-n' to go
     forwards.

   * multiple languages

     Different channels and servers may have different language
     encodings.

     In addition, it is possible to translate the messages that ERC
     uses into multiple languages.  Please contact the developers of
     ERC at <erc-discussATgnu.org> if you are interested in helping with
     the translation effort.

   * user scripting

     Users can load scripts (e.g. auto greeting scripts) when ERC
     starts up.

     It is also possible to make custom IRC commands, if you know a
     little Emacs Lisp.  Just make an Emacs Lisp function and call it
     `erc-cmd-NEWCOMMAND', where `NEWCOMMAND' is the name of the new
     command in capital letters.

   * auto reconnect

     If the connection goes away at some point, ERC will try to
     reconnect automatically.  If it fails to reconnect, and you want
     to try to manually reestablish the connection at some later point,
     switch to an ERC  buffer and run the `/RECONNECT' command.


File: erc,  Node: Keystroke Summary,  Next: Modules,  Prev: Getting Started,  Up: Top

5 Keys Used in ERC
******************

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


File: erc,  Node: Modules,  Next: Advanced Usage,  Prev: Keystroke Summary,  Up: Top

6 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
`M-x customize-option erc-modules RET'.  Alternatively, set
`erc-modules' manually and then call `erc-update-modules'.

   The following is a list of available modules.

`autoaway'
     Set away status automatically

`autojoin'
     Join channels automatically

`bbdb'
     Integrate with the Big Brother Database

`button'
     Buttonize URLs, nicknames, and other text

`capab-identify'
     Mark unidentified users on freenode and other servers supporting
     CAPAB.

`completion (aka pcomplete)'
     Complete nicknames and commands (programmable)

`fill'
     Wrap long lines

`hecomplete'
     Complete nicknames and commands (old).  This is the old module--you
     might prefer the "completion" module instead.

`identd'
     Launch an identd server on port 8113

`irccontrols'
     Highlight or remove IRC control characters

`log'
     Save buffers in logs

`match'
     Highlight pals, fools, and other keywords

`menu'
     Display a menu in ERC buffers

`netsplit'
     Detect netsplits

`noncommands'
     Don't display non-IRC commands after evaluation

`notify'
     Notify when the online status of certain users changes

`page'
     Process CTCP PAGE requests from IRC

`readonly'
     Make displayed lines read-only

`replace'
     Replace text in messages

`ring'
     Enable an input history

`scrolltobottom'
     Scroll to the bottom of the buffer

`services'
     Identify to Nickserv (IRC Services) automatically

`smiley'
     Convert smileys to pretty icons

`sound'
     Play sounds when you receive CTCP SOUND requests

`spelling'
     Check spelling of messages

`stamp'
     Add timestamps to messages

`track'
     Track channel activity in the mode-line

`truncate'
     Truncate buffers to a certain size

`unmorse'
     Translate morse code in messages


File: erc,  Node: Advanced Usage,  Next: Getting Help and Reporting Bugs,  Prev: Modules,  Up: Top

7 Advanced Usage
****************

* Menu:

* Connecting::                  Ways of connecting to an IRC server.
* Sample Configuration::        An example configuration file.
* Options::                     Options that are available for ERC.

File: erc,  Node: Connecting,  Next: Sample Configuration,  Prev: Advanced Usage,  Up: Advanced Usage

7.1 Connecting to an IRC Server
===============================

The easiest way to connect to an IRC server is to call `M-x erc'.  If
you want to assign this function to a keystroke, the following will
help you figure out its parameters.

 -- Function: erc
     Select connection parameters and run ERC.  Non-interactively, it
     takes the following keyword arguments.

        * SERVER

        * PORT

        * NICK

        * PASSWORD

        * FULL-NAME

     That is, if called with the following arguments, SERVER and
     FULL-NAME will be set to those values, whereas `erc-compute-port',
     `erc-compute-nick' and `erc-compute-full-name' will be invoked for
     the values of the other parameters.

          (erc :server "irc.freenode.net" :full-name "Harry S Truman")

Server
------

 -- Function: erc-compute-server &optional server
     Return an IRC server name.

     This tries a number of increasingly more default methods until a
     non-nil value is found.

        * SERVER (the argument passed to this function)

        * The `erc-server' option

        * The value of the IRCSERVER environment variable

        * The `erc-default-server' variable


 -- User Option: erc-server nil
     IRC server to use if one is not provided.

Port
----

 -- Function: erc-compute-port &optional port
     Return a port for an IRC server.

     This tries a number of increasingly more default methods until a
     non-nil value is found.

        * PORT (the argument passed to this function)

        * The `erc-port' option

        * The `erc-default-port' variable


 -- User Option: erc-port
     IRC port to use if not specified.

     This can be either a string or a number.

Nick
----

 -- Function: erc-compute-nick &optional nick
     Return user's IRC nick.

     This tries a number of increasingly more default methods until a
     non-nil value is found.

        * NICK (the argument passed to this function)

        * The `erc-nick' option

        * The value of the IRCNICK environment variable

        * The result from the `user-login-name' function


 -- User Option: erc-nick
     Nickname to use if one is not provided.

     This can be either a string, or a list of strings.  In the latter
     case, if the first nick in the list is already in use, other nicks
     are tried in the list order.

 -- User Option: erc-nick-uniquifier
     The string to append to the nick if it is already in use.

 -- User Option: erc-try-new-nick-p
     If the nickname you chose isn't available, and this option is
     non-nil, ERC should automatically attempt to connect with another
     nickname.

     You can manually set another nickname with the /NICK command.

Full name
---------

 -- Function: erc-compute-full-name &optional full-name
     Return user's full name.

     This tries a number of increasingly more default methods until a
     non-nil value is found.

        * FULL-NAME (the argument passed to this function)

        * The `erc-user-full-name' option

        * The value of the IRCNAME environment variable

        * The result from the `user-full-name' function


 -- User Option: erc-user-full-name
     User full name.

     This can be either a string or a function to call.

File: erc,  Node: Sample Configuration,  Next: Options,  Prev: Connecting,  Up: Advanced Usage

7.2 Sample Configuration
========================

Here is an example of configuration settings for ERC.  This can go into
your Emacs configuration file.  Everything after the `(require 'erc)'
command can optionally go into `~/.emacs.d/.ercrc.el'.

     ;;; Sample ERC configuration

     ;; Add the ERC directory to load path -- you don't need this if you are
     ;; using the version of ERC that comes with Emacs
     (add-to-list 'load-path "~/elisp/erc")

     ;; Load ERC
     (require 'erc)

     ;; Load authentication info from an external source.  Put sensitive
     ;; passwords and the like in here.
     (load "~/.emacs.d/.erc-auth")

     ;; This is an example of how to make a new command.  Type "/uptime" to
     ;; use it.
     (defun erc-cmd-UPTIME (&rest ignore)
       "Display the uptime of the system, as well as some load-related
     stuff, to the current ERC buffer."
       (let ((uname-output
              (replace-regexp-in-string
               ", load average: " "] {Load average} ["
               ;; Collapse spaces, remove
               (replace-regexp-in-string
                " +" " "
                ;; Remove beginning and trailing whitespace
                (replace-regexp-in-string
                 "^ +\\|[ \n]+$" ""
                 (shell-command-to-string "uptime"))))))
         (erc-send-message
          (concat "{Uptime} [" uname-output "]"))))

     ;; This causes ERC to connect to the Freenode network upon hitting
     ;; C-c e f.  Replace MYNICK with your IRC nick.
     (global-set-key "\C-cef" (lambda () (interactive)
                                (erc :server "irc.freenode.net" :port "6667"
                                     :nick "MYNICK")))

     ;; This causes ERC to connect to the IRC server on your own machine (if
     ;; you have one) upon hitting C-c e b.  Replace MYNICK with your IRC
     ;; nick.  Often, people like to run bitlbee (http://bitlbee.org/) as an
     ;; AIM/Jabber/MSN to IRC gateway, so that they can use ERC to chat with
     ;; people on those networks.
     (global-set-key "\C-ceb" (lambda () (interactive)
                                (erc :server "localhost" :port "6667"
                                     :nick "MYNICK")))

     ;; Make C-c RET (or C-c C-RET) send messages instead of RET. This has
     ;; been commented out to avoid confusing new users.
     ;; (define-key erc-mode-map (kbd "RET") nil)
     ;; (define-key erc-mode-map (kbd "C-c RET") 'erc-send-current-line)
     ;; (define-key erc-mode-map (kbd "C-c C-RET") 'erc-send-current-line)

     ;;; Options

     ;; Join the #emacs and #erc channels whenever connecting to Freenode.
     (setq erc-autojoin-channels-alist '(("freenode.net" "#emacs" "#erc")))

     ;; Interpret mIRC-style color commands in IRC chats
     (setq erc-interpret-mirc-color t)

     ;; The following are commented out by default, but users of other
     ;; non-Emacs IRC clients might find them useful.
     ;; Kill buffers for channels after /part
     ;; (setq erc-kill-buffer-on-part t)
     ;; Kill buffers for private queries after quitting the server
     ;; (setq erc-kill-queries-on-quit t)
     ;; Kill buffers for server messages after quitting the server
     ;; (setq erc-kill-server-buffer-on-quit t)

File: erc,  Node: Options,  Prev: Sample Configuration,  Up: Advanced Usage

7.3 Options
===========

This section has not yet been written.  For now, the easiest way to
check out the available options for ERC is to do `M-x customize-group
erc RET'.

File: erc,  Node: Getting Help and Reporting Bugs,  Next: History,  Prev: Advanced Usage,  Up: Top

8 Getting Help and Reporting Bugs
*********************************

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.

   * `http://www.emacswiki.org/cgi-bin/wiki/ERC' is the emacswiki.org
     page for ERC.  Anyone may add tips, hints, or bug descriptions to
     it.

   * There are several mailing lists for ERC.  To subscribe, visit
     `http://savannah.gnu.org/mail/?group=erc'.

     The mailing lists are also available on Gmane.
     (`http://gmane.org/').  Gmane provides additional methods for
     accessing the mailing lists, adding content to them, and searching
     them.

       1. gmane.emacs.erc.announce: Announcements

       2. gmane.emacs.erc.discuss: General discussion

       3. gmane.emacs.erc.cvs: Log messages for changes to the ERC
          source code


   * You can visit the IRC Freenode channel `#emacs'. Many of the
     contributors are frequently around and willing to answer your
     questions.


File: erc,  Node: History,  Next: Copying,  Prev: Getting Help and Reporting Bugs,  Up: Top

9 History
*********

ERC was originally written by Alexander L. Belikoff <abelATbfr.il>
and Sergey Berezin <sergey.berezinATcs.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.

   * 2001

     In June 2001, Mario Lang <mlangATdelysid.org> and Alex Schroeder
     <alexATgnu.org> took over development and created a ERC Project at
     `http://sourceforge.net/projects/erc'.

     In reaction to a mail about the new ERC development effort, 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 happened on #emacs on
     irc.openprojects.net.  Over time, many people contributed code,
     ideas, bugfixes, and a lot of alpha/beta/gamma testing.

     See the `CREDITS' file for a list of contributors.

   * 2003

     ERC 3.0 was released.

   * 2004

     ERC 4.0 was released.

   * 2005

     ERC 5.0 was released.  Michael Olson <mwolsonATgnu.org> became the
     release manager and eventually the maintainer.

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

   * 2006

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

     ERC became an official GNU project, and development moved to
     `http://sv.gnu.org/projects/erc'.  We switched to using GNU Arch as
     our revision control system.  Our mailing list address changed as
     well.

   * 2007

     We switched to using git for our version control system.


File: erc,  Node: Copying,  Next: GNU Free Documentation License,  Prev: History,  Up: Top

                        Version 3, 29 June 2007

     Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'

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

Preamble
========

The GNU General Public License is a free, copyleft license for software
and other kinds of works.

   The licenses for most software and other practical works are designed
to take away your freedom to share and change the works.  By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains
free software for all its users.  We, the Free Software Foundation, use
the GNU General Public License for most of our software; it applies
also to any other work released this way by its authors.  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
them 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 prevent others from denying you
these rights or asking you to surrender the rights.  Therefore, you
have certain responsibilities if you distribute copies of the software,
or if you modify it: responsibilities to respect the freedom of others.

   For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received.  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.

   Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

   For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software.  For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

   Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so.  This is fundamentally incompatible with the
aim of protecting users' freedom to change the software.  The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products.  If such problems arise substantially in
other domains, we stand ready to extend this provision to those domains
in future versions of the GPL, as needed to protect the freedom of
users.

   Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary.  To prevent this, the GPL assures that
patents cannot be used to render the program non-free.

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

TERMS AND CONDITIONS
====================

  0. Definitions.

     "This License" refers to version 3 of the GNU General Public
     License.

     "Copyright" also means copyright-like laws that apply to other
     kinds of works, such as semiconductor masks.

     "The Program" refers to any copyrightable work licensed under this
     License.  Each licensee is addressed as "you".  "Licensees" and
     "recipients" may be individuals or organizations.

     To "modify" a work means to copy from or adapt all or part of the
     work in a fashion requiring copyright permission, other than the
     making of an exact copy.  The resulting work is called a "modified
     version" of the earlier work or a work "based on" the earlier work.

     A "covered work" means either the unmodified Program or a work
     based on the Program.

     To "propagate" a work means to do anything with it that, without
     permission, would make you directly or secondarily liable for
     infringement under applicable copyright law, except executing it
     on a computer or modifying a private copy.  Propagation includes
     copying, distribution (with or without modification), making
     available to the public, and in some countries other activities as
     well.

     To "convey" a work means any kind of propagation that enables other
     parties to make or receive copies.  Mere interaction with a user
     through a computer network, with no transfer of a copy, is not
     conveying.

     An interactive user interface displays "Appropriate Legal Notices"
     to the extent that it includes a convenient and prominently visible
     feature that (1) displays an appropriate copyright notice, and (2)
     tells the user that there is no warranty for the work (except to
     the extent that warranties are provided), that licensees may
     convey the work under this License, and how to view a copy of this
     License.  If the interface presents a list of user commands or
     options, such as a menu, a prominent item in the list meets this
     criterion.

  1. Source Code.

     The "source code" for a work means the preferred form of the work
     for making modifications to it.  "Object code" means any
     non-source form of a work.

     A "Standard Interface" means an interface that either is an
     official standard defined by a recognized standards body, or, in
     the case of interfaces specified for a particular programming
     language, one that is widely used among developers working in that
     language.

     The "System Libraries" of an executable work include anything,
     other than the work as a whole, that (a) is included in the normal
     form of packaging a Major Component, but which is not part of that
     Major Component, and (b) serves only to enable use of the work
     with that Major Component, or to implement a Standard Interface
     for which an implementation is available to the public in source
     code form.  A "Major Component", in this context, means a major
     essential component (kernel, window system, and so on) of the
     specific operating system (if any) on which the executable work
     runs, or a compiler used to produce the work, or an object code
     interpreter used to run it.

     The "Corresponding Source" for a work in object code form means all
     the source code needed to generate, install, and (for an executable
     work) run the object code and to modify the work, including
     scripts to control those activities.  However, it does not include
     the work's System Libraries, or general-purpose tools or generally
     available free programs which are used unmodified in performing
     those activities but which are not part of the work.  For example,
     Corresponding Source includes interface definition files
     associated with source files for the work, and the source code for
     shared libraries and dynamically linked subprograms that the work
     is specifically designed to require, such as by intimate data
     communication or control flow between those subprograms and other
     parts of the work.

     The Corresponding Source need not include anything that users can
     regenerate automatically from other parts of the Corresponding
     Source.

     The Corresponding Source for a work in source code form is that
     same work.

  2. Basic Permissions.

     All rights granted under this License are granted for the term of
     copyright on the Program, and are irrevocable provided the stated
     conditions are met.  This License explicitly affirms your unlimited
     permission to run the unmodified Program.  The output from running
     a covered work is covered by this License only if the output,
     given its content, constitutes a covered work.  This License
     acknowledges your rights of fair use or other equivalent, as
     provided by copyright law.

     You may make, run and propagate covered works that you do not
     convey, without conditions so long as your license otherwise
     remains in force.  You may convey covered works to others for the
     sole purpose of having them make modifications exclusively for
     you, or provide you with facilities for running those works,
     provided that you comply with the terms of this License in
     conveying all material for which you do not control copyright.
     Those thus making or running the covered works for you must do so
     exclusively on your behalf, under your direction and control, on
     terms that prohibit them from making any copies of your
     copyrighted material outside their relationship with you.

     Conveying under any other circumstances is permitted solely under
     the conditions stated below.  Sublicensing is not allowed; section
     10 makes it unnecessary.

  3. Protecting Users' Legal Rights From Anti-Circumvention Law.

     No covered work shall be deemed part of an effective technological
     measure under any applicable law fulfilling obligations under
     article 11 of the WIPO copyright treaty adopted on 20 December
     1996, or similar laws prohibiting or restricting circumvention of
     such measures.

     When you convey a covered work, you waive any legal power to forbid
     circumvention of technological measures to the extent such
     circumvention is effected by exercising rights under this License
     with respect to the covered work, and you disclaim any intention
     to limit operation or modification of the work as a means of
     enforcing, against the work's users, your or third parties' legal
     rights to forbid circumvention of technological measures.

  4. Conveying Verbatim Copies.

     You may convey 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;
     keep intact all notices stating that this License and any
     non-permissive terms added in accord with section 7 apply to the
     code; keep intact all notices of the absence of any warranty; and
     give all recipients a copy of this License along with the Program.

     You may charge any price or no price for each copy that you convey,
     and you may offer support or warranty protection for a fee.

  5. Conveying Modified Source Versions.

     You may convey a work based on the Program, or the modifications to
     produce it from the Program, in the form of source code under the
     terms of section 4, provided that you also meet all of these
     conditions:

       a. The work must carry prominent notices stating that you
          modified it, and giving a relevant date.

       b. The work must carry prominent notices stating that it is
          released under this License and any conditions added under
          section 7.  This requirement modifies the requirement in
          section 4 to "keep intact all notices".

       c. You must license the entire work, as a whole, under this
          License to anyone who comes into possession of a copy.  This
          License will therefore apply, along with any applicable
          section 7 additional terms, to the whole of the work, and all
          its parts, regardless of how they are packaged.  This License
          gives no permission to license the work in any other way, but
          it does not invalidate such permission if you have separately
          received it.

       d. If the work has interactive user interfaces, each must display
          Appropriate Legal Notices; however, if the Program has
          interactive interfaces that do not display Appropriate Legal
          Notices, your work need not make them do so.

     A compilation of a covered work with other separate and independent
     works, which are not by their nature extensions of the covered
     work, and which are not combined with it such as to form a larger
     program, in or on a volume of a storage or distribution medium, is
     called an "aggregate" if the compilation and its resulting
     copyright are not used to limit the access or legal rights of the
     compilation's users beyond what the individual works permit.
     Inclusion of a covered work in an aggregate does not cause this
     License to apply to the other parts of the aggregate.

  6. Conveying Non-Source Forms.

     You may convey a covered work in object code form under the terms
     of sections 4 and 5, provided that you also convey the
     machine-readable Corresponding Source under the terms of this
     License, in one of these ways:

       a. Convey the object code in, or embodied in, a physical product
          (including a physical distribution medium), accompanied by the
          Corresponding Source fixed on a durable physical medium
          customarily used for software interchange.

       b. Convey the object code in, or embodied in, a physical product
          (including a physical distribution medium), accompanied by a
          written offer, valid for at least three years and valid for
          as long as you offer spare parts or customer support for that
          product model, to give anyone who possesses the object code
          either (1) a copy of the Corresponding Source for all the
          software in the product that is covered by this License, on a
          durable physical medium customarily used for software
          interchange, for a price no more than your reasonable cost of
          physically performing this conveying of source, or (2) access
          to copy the Corresponding Source from a network server at no
          charge.

       c. Convey individual copies of the object code with a copy of
          the written offer to provide the Corresponding Source.  This
          alternative is allowed only occasionally and noncommercially,
          and only if you received the object code with such an offer,
          in accord with subsection 6b.

       d. Convey the object code by offering access from a designated
          place (gratis or for a charge), and offer equivalent access
          to the Corresponding Source in the same way through the same
          place at no further charge.  You need not require recipients
          to copy the Corresponding Source along with the object code.
          If the place to copy the object code is a network server, the
          Corresponding Source may be on a different server (operated
          by you or a third party) that supports equivalent copying
          facilities, provided you maintain clear directions next to
          the object code saying where to find the Corresponding Source.
          Regardless of what server hosts the Corresponding Source, you
          remain obligated to ensure that it is available for as long
          as needed to satisfy these requirements.

       e. Convey the object code using peer-to-peer transmission,
          provided you inform other peers where the object code and
          Corresponding Source of the work are being offered to the
          general public at no charge under subsection 6d.


     A separable portion of the object code, whose source code is
     excluded from the Corresponding Source as a System Library, need
     not be included in conveying the object code work.

     A "User Product" is either (1) a "consumer product", which means
     any tangible personal property which is normally used for personal,
     family, or household purposes, or (2) anything designed or sold for
     incorporation into a dwelling.  In determining whether a product
     is a consumer product, doubtful cases shall be resolved in favor of
     coverage.  For a particular product received by a particular user,
     "normally used" refers to a typical or common use of that class of
     product, regardless of the status of the particular user or of the
     way in which the particular user actually uses, or expects or is
     expected to use, the product.  A product is a consumer product
     regardless of whether the product has substantial commercial,
     industrial or non-consumer uses, unless such uses represent the
     only significant mode of use of the product.

     "Installation Information" for a User Product means any methods,
     procedures, authorization keys, or other information required to
     install and execute modified versions of a covered work in that
     User Product from a modified version of its Corresponding Source.
     The information must suffice to ensure that the continued
     functioning of the modified object code is in no case prevented or
     interfered with solely because modification has been made.

     If you convey an object code work under this section in, or with,
     or specifically for use in, a User Product, and the conveying
     occurs as part of a transaction in which the right of possession
     and use of the User Product is transferred to the recipient in
     perpetuity or for a fixed term (regardless of how the transaction
     is characterized), the Corresponding Source conveyed under this
     section must be accompanied by the Installation Information.  But
     this requirement does not apply if neither you nor any third party
     retains the ability to install modified object code on the User
     Product (for example, the work has been installed in ROM).

     The requirement to provide Installation Information does not
     include a requirement to continue to provide support service,
     warranty, or updates for a work that has been modified or
     installed by the recipient, or for the User Product in which it
     has been modified or installed.  Access to a network may be denied
     when the modification itself materially and adversely affects the
     operation of the network or violates the rules and protocols for
     communication across the network.

     Corresponding Source conveyed, and Installation Information
     provided, in accord with this section must be in a format that is
     publicly documented (and with an implementation available to the
     public in source code form), and must require no special password
     or key for unpacking, reading or copying.

  7. Additional Terms.

     "Additional permissions" are terms that supplement the terms of
     this License by making exceptions from one or more of its
     conditions.  Additional permissions that are applicable to the
     entire Program shall be treated as though they were included in
     this License, to the extent that they are valid under applicable
     law.  If additional permissions apply only to part of the Program,
     that part may be used separately under those permissions, but the
     entire Program remains governed by this License without regard to
     the additional permissions.

     When you convey a copy of a covered work, you may at your option
     remove any additional permissions from that copy, or from any part
     of it.  (Additional permissions may be written to require their own
     removal in certain cases when you modify the work.)  You may place
     additional permissions on material, added by you to a covered work,
     for which you have or can give appropriate copyright permission.

     Notwithstanding any other provision of this License, for material
     you add to a covered work, you may (if authorized by the copyright
     holders of that material) supplement the terms of this License
     with terms:

       a. Disclaiming warranty or limiting liability differently from
          the terms of sections 15 and 16 of this License; or

       b. Requiring preservation of specified reasonable legal notices
          or author attributions in that material or in the Appropriate
          Legal Notices displayed by works containing it; or

       c. Prohibiting misrepresentation of the origin of that material,
          or requiring that modified versions of such material be
          marked in reasonable ways as different from the original
          version; or

       d. Limiting the use for publicity purposes of names of licensors
          or authors of the material; or

       e. Declining to grant rights under trademark law for use of some
          trade names, trademarks, or service marks; or

       f. Requiring indemnification of licensors and authors of that
          material by anyone who conveys the material (or modified
          versions of it) with contractual assumptions of liability to
          the recipient, for any liability that these contractual
          assumptions directly impose on those licensors and authors.

     All other non-permissive additional terms are considered "further
     restrictions" within the meaning of section 10.  If the Program as
     you received it, or any part of it, contains a notice stating that
     it is governed by this License along with a term that is a further
     restriction, you may remove that term.  If a license document
     contains a further restriction but permits relicensing or
     conveying under this License, you may add to a covered work
     material governed by the terms of that license document, provided
     that the further restriction does not survive such relicensing or
     conveying.

     If you add terms to a covered work in accord with this section, you
     must place, in the relevant source files, a statement of the
     additional terms that apply to those files, or a notice indicating
     where to find the applicable terms.

     Additional terms, permissive or non-permissive, may be stated in
     the form of a separately written license, or stated as exceptions;
     the above requirements apply either way.

  8. Termination.

     You may not propagate or modify a covered work except as expressly
     provided under this License.  Any attempt otherwise to propagate or
     modify it is void, and will automatically terminate your rights
     under this License (including any patent licenses granted under
     the third paragraph of section 11).

     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
     copyright holder fails to notify you of the violation by some
     reasonable means prior to 60 days after the cessation.

     Moreover, your license from a particular copyright holder is
     reinstated permanently if the copyright holder notifies you of the
     violation by some reasonable means, this is the first time you have
     received notice of violation of this License (for any work) from
     that copyright holder, and you cure the violation prior to 30 days
     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, you do not qualify to receive new
     licenses for the same material under section 10.

  9. Acceptance Not Required for Having Copies.

     You are not required to accept this License in order to receive or
     run a copy of the Program.  Ancillary propagation of a covered work
     occurring solely as a consequence of using peer-to-peer
     transmission to receive a copy likewise does not require
     acceptance.  However, nothing other than this License grants you
     permission to propagate or modify any covered work.  These actions
     infringe copyright if you do not accept this License.  Therefore,
     by modifying or propagating a covered work, you indicate your
     acceptance of this License to do so.

 10. Automatic Licensing of Downstream Recipients.

     Each time you convey a covered work, the recipient automatically
     receives a license from the original licensors, to run, modify and
     propagate that work, subject to this License.  You are not
     responsible for enforcing compliance by third parties with this
     License.

     An "entity transaction" is a transaction transferring control of an
     organization, or substantially all assets of one, or subdividing an
     organization, or merging organizations.  If propagation of a
     covered work results from an entity transaction, each party to that
     transaction who receives a copy of the work also receives whatever
     licenses to the work the party's predecessor in interest had or
     could give under the previous paragraph, plus a right to
     possession of the Corresponding Source of the work from the
     predecessor in interest, if the predecessor has it or can get it
     with reasonable efforts.

     You may not impose any further restrictions on the exercise of the
     rights granted or affirmed under this License.  For example, you
     may not impose a license fee, royalty, or other charge for
     exercise of rights granted under this License, and you may not
     initiate litigation (including a cross-claim or counterclaim in a
     lawsuit) alleging that any patent claim is infringed by making,
     using, selling, offering for sale, or importing the Program or any
     portion of it.

 11. Patents.

     A "contributor" is a copyright holder who authorizes use under this
     License of the Program or a work on which the Program is based.
     The work thus licensed is called the contributor's "contributor
     version".

     A contributor's "essential patent claims" are all patent claims
     owned or controlled by the contributor, whether already acquired or
     hereafter acquired, that would be infringed by some manner,
     permitted by this License, of making, using, or selling its
     contributor version, but do not include claims that would be
     infringed only as a consequence of further modification of the
     contributor version.  For purposes of this definition, "control"
     includes the right to grant patent sublicenses in a manner
     consistent with the requirements of this License.

     Each contributor grants you a non-exclusive, worldwide,
     royalty-free patent license under the contributor's essential
     patent claims, to make, use, sell, offer for sale, import and
     otherwise run, modify and propagate the contents of its
     contributor version.

     In the following three paragraphs, a "patent license" is any
     express agreement or commitment, however denominated, not to
     enforce a patent (such as an express permission to practice a
     patent or covenant not to sue for patent infringement).  To
     "grant" such a patent license to a party means to make such an
     agreement or commitment not to enforce a patent against the party.

     If you convey a covered work, knowingly relying on a patent
     license, and the Corresponding Source of the work is not available
     for anyone to copy, free of charge and under the terms of this
     License, through a publicly available network server or other
     readily accessible means, then you must either (1) cause the
     Corresponding Source to be so available, or (2) arrange to deprive
     yourself of the benefit of the patent license for this particular
     work, or (3) arrange, in a manner consistent with the requirements
     of this License, to extend the patent license to downstream
     recipients.  "Knowingly relying" means you have actual knowledge
     that, but for the patent license, your conveying the covered work
     in a country, or your recipient's use of the covered work in a
     country, would infringe one or more identifiable patents in that
     country that you have reason to believe are valid.

     If, pursuant to or in connection with a single transaction or
     arrangement, you convey, or propagate by procuring conveyance of, a
     covered work, and grant a patent license to some of the parties
     receiving the covered work authorizing them to use, propagate,
     modify or convey a specific copy of the covered work, then the
     patent license you grant is automatically extended to all
     recipients of the covered work and works based on it.

     A patent license is "discriminatory" if it does not include within
     the scope of its coverage, prohibits the exercise of, or is
     conditioned on the non-exercise of one or more of the rights that
     are specifically granted under this License.  You may not convey a
     covered work if you are a party to an arrangement with a third
     party that is in the business of distributing software, under
     which you make payment to the third party based on the extent of
     your activity of conveying the work, and under which the third
     party grants, to any of the parties who would receive the covered
     work from you, a discriminatory patent license (a) in connection
     with copies of the covered work conveyed by you (or copies made
     from those copies), or (b) primarily for and in connection with
     specific products or compilations that contain the covered work,
     unless you entered into that arrangement, or that patent license
     was granted, prior to 28 March 2007.

     Nothing in this License shall be construed as excluding or limiting
     any implied license or other defenses to infringement that may
     otherwise be available to you under applicable patent law.

 12. No Surrender of Others' Freedom.

     If 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 convey a covered work so as to satisfy
     simultaneously your obligations under this License and any other
     pertinent obligations, then as a consequence you may not convey it
     at all.  For example, if you agree to terms that obligate you to
     collect a royalty for further conveying from those to whom you
     convey the Program, the only way you could satisfy both those
     terms and this License would be to refrain entirely from conveying
     the Program.

 13. Use with the GNU Affero General Public License.

     Notwithstanding any other provision of this License, you have
     permission to link or combine any covered work with a work licensed
     under version 3 of the GNU Affero General Public License into a
     single combined work, and to convey the resulting work.  The terms
     of this License will continue to apply to the part which is the
     covered work, but the special requirements of the GNU Affero
     General Public License, section 13, concerning interaction through
     a network will apply to the combination as such.

 14. Revised Versions of this License.

     The Free Software Foundation may publish revised and/or new
     versions of the GNU 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 that a certain numbered version of the GNU
     General Public License "or any later version" applies to it, you
     have the option of following the terms and conditions either of
     that numbered version or of any later version published by the
     Free Software Foundation.  If the Program does not specify a
     version number of the GNU General Public License, you may choose
     any version ever published by the Free Software Foundation.

     If the Program specifies that a proxy can decide which future
     versions of the GNU General Public License can be used, that
     proxy's public statement of acceptance of a version permanently
     authorizes you to choose that version for the Program.

     Later license versions may give you additional or different
     permissions.  However, no additional obligations are imposed on any
     author or copyright holder as a result of your choosing to follow a
     later version.

 15. Disclaimer of Warranty.

     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.

 16. Limitation of Liability.

     IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
     WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
     AND/OR CONVEYS 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.

 17. Interpretation of Sections 15 and 16.

     If the disclaimer of warranty and limitation of liability provided
     above cannot be given local legal effect according to their terms,
     reviewing courts shall apply local law that most closely
     approximates an absolute waiver of all civil liability in
     connection with the Program, unless a warranty or assumption of
     liability accompanies a copy of the Program in return for a fee.


END OF TERMS AND CONDITIONS
===========================

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
state the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

     ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
     Copyright (C) YEAR 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 3 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, see `http://www.gnu.org/licenses/'.

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

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

     PROGRAM Copyright (C) YEAR NAME OF AUTHOR
     This program 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.

   The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License.  Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".

   You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  For more information on this, and how to apply and follow
the GNU GPL, see `http://www.gnu.org/licenses/'.

   The GNU 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 Lesser General Public License instead of this License.  But first,
please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.

File: erc,  Node: GNU Free Documentation License,  Next: Concept Index,  Prev: Copying,  Up: Top

                     Version 1.3, 3 November 2008

     Copyright (C) 2000, 2001, 2002, 2007, 2008, 2009 Free Software Foundation, Inc.
     `http://fsf.org/'

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

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

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

     The "publisher" means any person or entity that distributes copies
     of the Document to the public.

     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.

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

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

  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:

       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.

     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.

  5. 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."

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

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

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

  9. TERMINATION

     You may not copy, modify, sublicense, or distribute the Document
     except as expressly provided under this License.  Any attempt
     otherwise to copy, modify, sublicense, or distribute it is void,
     and will automatically terminate your rights under this License.

     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
     copyright holder fails to notify you of the violation by some
     reasonable means prior to 60 days after the cessation.

     Moreover, your license from a particular copyright holder is
     reinstated permanently if the copyright holder notifies you of the
     violation by some reasonable means, this is the first time you have
     received notice of violation of this License (for any work) from
     that copyright holder, and you cure the violation prior to 30 days
     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.

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

     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
     proxy's public statement of acceptance of a version permanently
     authorizes you to choose that version for the Document.

 11. RELICENSING

     "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
     World Wide Web server that publishes copyrightable works and also
     provides prominent facilities for anybody to edit those works.  A
     public wiki that anybody can edit is an example of such a server.
     A "Massive Multiauthor Collaboration" (or "MMC") contained in the
     site means any set of copyrightable works thus published on the MMC
     site.

     "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
     license published by Creative Commons Corporation, a not-for-profit
     corporation with a principal place of business in San Francisco,
     California, as well as future copyleft versions of that license
     published by that same organization.

     "Incorporate" means to publish or republish a Document, in whole or
     in part, as part of another Document.

     An MMC is "eligible for relicensing" if it is licensed under this
     License, and if all works that were first published under this
     License somewhere other than this MMC, and subsequently
     incorporated in whole or in part into the MMC, (1) had no cover
     texts or invariant sections, and (2) were thus incorporated prior
     to November 1, 2008.

     The operator of an MMC Site may republish an MMC contained in the
     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
====================================================

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:

       Copyright (C)  YEAR  YOUR NAME.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.3
       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''.

   If you have Invariant Sections, Front-Cover Texts and Back-Cover
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
         being LIST.

   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.

File: erc,  Node: Concept Index,  Prev: GNU Free Documentation License,  Up: Top

Index
*****

[index]
* Menu:

* advanced topics:                       Advanced Usage.      (line   6)
* bugs, reporting:                       Getting Help and Reporting Bugs.
                                                              (line   6)
* configuration, sample:                 Sample Configuration.
                                                              (line   6)
* connecting:                            Connecting.          (line   6)
* Debian package for ERC:                Releases.            (line  12)
* development:                           Development.         (line   6)
* erc:                                   Connecting.          (line  11)
* erc-compute-full-name:                 Connecting.          (line 112)
* erc-compute-nick:                      Connecting.          (line  77)
* erc-compute-port:                      Connecting.          (line  56)
* erc-compute-server:                    Connecting.          (line  35)
* git version control system, using:     Development.         (line   9)
* help, getting:                         Getting Help and Reporting Bugs.
                                                              (line   6)
* history ring:                          Special Features.    (line  39)
* history, of ERC:                       History.             (line   6)
* keystrokes:                            Keystroke Summary.   (line   6)
* modules:                               Modules.             (line   6)
* modules, autoaway:                     Modules.             (line  15)
* modules, autojoin:                     Modules.             (line  18)
* modules, bbdb:                         Modules.             (line  21)
* modules, button:                       Modules.             (line  24)
* modules, capab-identify:               Modules.             (line  27)
* modules, completion:                   Modules.             (line  31)
* modules, fill:                         Modules.             (line  34)
* modules, hecomplete:                   Modules.             (line  37)
* modules, identd:                       Modules.             (line  41)
* modules, irccontrols:                  Modules.             (line  44)
* modules, log:                          Modules.             (line  47)
* modules, match:                        Modules.             (line  50)
* modules, menu:                         Modules.             (line  53)
* modules, netsplit:                     Modules.             (line  56)
* modules, noncommands:                  Modules.             (line  59)
* modules, notify:                       Modules.             (line  62)
* modules, page:                         Modules.             (line  65)
* modules, pcomplete:                    Modules.             (line  31)
* modules, readonly:                     Modules.             (line  68)
* modules, replace:                      Modules.             (line  71)
* modules, ring:                         Modules.             (line  74)
* modules, scrolltobottom:               Modules.             (line  77)
* modules, services:                     Modules.             (line  80)
* modules, smiley:                       Modules.             (line  83)
* modules, sound:                        Modules.             (line  86)
* modules, spelling:                     Modules.             (line  89)
* modules, stamp:                        Modules.             (line  92)
* modules, track:                        Modules.             (line  95)
* modules, truncate:                     Modules.             (line  98)
* modules, unmorse:                      Modules.             (line 101)
* options:                               Options.             (line   6)
* query buffers:                         Special Features.    (line  13)
* releases, Debian package:              Releases.            (line  12)
* releases, from source:                 Releases.            (line  15)
* settings:                              Getting Started.     (line   6)
* updating ERC with git:                 Development.         (line  66)