[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] scratch/bbdb 251d2d1: Remove files with unclear copyright status;
|
From: |
Stefan Monnier |
|
Subject: |
[elpa] scratch/bbdb 251d2d1: Remove files with unclear copyright status; prepare for move to externals/ |
|
Date: |
Fri, 10 Nov 2017 12:24:23 -0500 (EST) |
branch: scratch/bbdb
commit 251d2d1fb94633a971d3079ef8daa5cb919f1216
Author: Stefan Monnier <address@hidden>
Commit: Stefan Monnier <address@hidden>
Remove files with unclear copyright status; prepare for move to externals/
---
GNUmakefile | 27 ++
Makefile.am | 42 --
bbdb-gnus.el | 400 ------------------
bbdb-sc.el | 196 ---------
bbdb-vm.el | 344 ----------------
bbdb.el | 2 +-
bbdb.info | 1283 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
dir | 20 +
8 files changed, 1331 insertions(+), 983 deletions(-)
diff --git a/GNUmakefile b/GNUmakefile
new file mode 100644
index 0000000..2b51ee4
--- /dev/null
+++ b/GNUmakefile
@@ -0,0 +1,27 @@
+# Rules to generate the files that need to go into the ELPA package.
+
+# Copied and adapted from AUCTeX's GNUmakefile.
+
+MAKEINFO=makeinfo
+INSTALL_INFO=install-info
+
+MANUALS=bbdb
+INFO_FILES=$(MANUALS:=.info)
+
+# FIXME: Currently these files need to be stored in the elpa.git repository
+# because the elpa.gnu.org scripts don't know how to build the Info file
+# from the Texinfo file.
+GENERATED_FILES=dir $(INFO_FILES)
+
+elpa: $(GENERATED_FILES)
+
+clean:
+ rm -f $(GENERATED_FILES)
+
+TEXI_SOURCES:=$(wildcard doc/*.texi)
+$(INFO_FILES): %.info: $(TEXI_SOURCES)
+ cd doc; $(MAKEINFO) --no-split $*.texi
+ mv doc/$*.info $@
+
+dir: $(INFO_FILES)
+ for f in $(INFO_FILES); do $(INSTALL_INFO) --info-dir=. $$f; done
diff --git a/Makefile.am b/Makefile.am
deleted file mode 100644
index 809d442..0000000
--- a/Makefile.am
+++ /dev/null
@@ -1,42 +0,0 @@
-# main Makefile.am for BBDB
-#
-# Copyright (C) 2013 Christian Egli <address@hidden>
-# Copyright (C) 2013-2017 Roland Winkler <address@hidden>
-#
-# This file is part of the Insidious Big Brother Database (aka BBDB),
-#
-# BBDB 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.
-#
-# BBDB 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 BBDB. If not, see <http://www.gnu.org/licenses/>.
-
-SUBDIRS = lisp doc tex
-
-doc_DATA = COPYING ChangeLog AUTHORS NEWS README TODO
-
-EXTRA_DIST = autogen.sh
-
-BBDB_ELPA_FILES = README COPYING lisp/*.el doc/*.info doc/dir tex/*.sty
-BBDB_ELPA_PACKAGE = bbdb-$(PACKAGE_VERSION).tar
-
-# doc/dir is needed for the ELPA package
-doc/dir: doc/bbdb.info
- install-info $< $@
-
-CLEANFILES = doc/dir
-
-# Package everything in a form suitable for ELPA.
-elpa: $(BBDB_ELPA_FILES)
- $(AMTAR) --transform='s:\(lisp\|doc\|tex\)/::' \
- --transform='s::bbdb-$(PACKAGE_VERSION)/:' \
- --exclude=bbdb-loaddefs.el \
- -cf $(BBDB_ELPA_PACKAGE) $(BBDB_ELPA_FILES)
- @echo "Created $(BBDB_ELPA_PACKAGE)"
diff --git a/bbdb-gnus.el b/bbdb-gnus.el
deleted file mode 100644
index 028cf9d..0000000
--- a/bbdb-gnus.el
+++ /dev/null
@@ -1,400 +0,0 @@
-;;; bbdb-gnus.el --- BBDB interface to Gnus -*- lexical-binding: t -*-
-
-;; Copyright (C) 1991, 1992, 1993 Jamie Zawinski <address@hidden>.
-;; Copyright (C) 2010-2017 Roland Winkler <address@hidden>
-
-;; This file is part of the Insidious Big Brother Database (aka BBDB),
-
-;; BBDB 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.
-
-;; BBDB 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 BBDB. If not, see <http://www.gnu.org/licenses/>.
-
-;;; Commentary:
-;; This file contains the BBDB interface to Gnus.
-;; See the BBDB info manual for documentation.
-
-;;; Code:
-
-(require 'bbdb)
-(require 'bbdb-com)
-(require 'bbdb-mua)
-(require 'gnus)
-
-(declare-function message-make-domain "message")
-
-;; Scoring
-
-(defcustom bbdb/gnus-score-field 'gnus-score
- "This variable contains the name of the BBDB field which should be
-checked for a score to add to the mail addresses in the same record."
- :group 'bbdb-mua-gnus-scoring
- :type 'symbol)
-
-(defcustom bbdb/gnus-score-default nil
- "If this is set, then every mail address in the BBDB that does not have
-an associated score field will be assigned this score. A value of nil
-implies a default score of zero."
- :group 'bbdb-mua-gnus-scoring
- :type '(choice (const :tag "Do not assign default score" nil)
- (integer :tag "Assign this default score" 0)))
-
-(defvar bbdb/gnus-score-default-internal nil
- "Internal variable for detecting changes to
-`bbdb/gnus-score-default'. You should not set this variable directly -
-set `bbdb/gnus-score-default' instead.")
-
-(defvar bbdb/gnus-score-alist nil
- "The text version of the scoring structure returned by
-bbdb/gnus-score. This is built automatically from the BBDB.")
-
-(defvar bbdb/gnus-score-rebuild-alist t
- "Set to t to rebuild bbdb/gnus-score-alist on the next call to
-bbdb/gnus-score. This will be set automatically if you change a BBDB
-record which contains a gnus-score field.")
-
-(defun bbdb/gnus-score-invalidate-alist (record)
- "This function is called through `bbdb-after-change-hook',
-and sets `bbdb/gnus-score-rebuild-alist' to t if the changed
-record contains a gnus-score field."
- (if (bbdb-record-xfield record bbdb/gnus-score-field)
- (setq bbdb/gnus-score-rebuild-alist t)))
-
-;;;###autoload
-(defun bbdb/gnus-score (group)
- "This returns a score alist for Gnus. A score pair will be made for
-every member of the mail field in records which also have a gnus-score
-field. This allows the BBDB to serve as a supplemental global score
-file, with the advantage that it can keep up with multiple and changing
-addresses better than the traditionally static global scorefile."
- (list (list
- (condition-case nil
- (read (bbdb/gnus-score-as-text group))
- (error (setq bbdb/gnus-score-rebuild-alist t)
- (message "Problem building BBDB score table.")
- (ding) (sit-for 2)
- nil)))))
-
-(defun bbdb/gnus-score-as-text (_group)
- "Returns a SCORE file format string built from the BBDB."
- (cond ((or (cond ((/= (or bbdb/gnus-score-default 0)
- (or bbdb/gnus-score-default-internal 0))
- (setq bbdb/gnus-score-default-internal
- bbdb/gnus-score-default)
- t))
- (not bbdb/gnus-score-alist)
- bbdb/gnus-score-rebuild-alist)
- (setq bbdb/gnus-score-rebuild-alist nil)
- (setq bbdb/gnus-score-alist
- (concat "((touched nil) (\"from\"\n"
- (mapconcat
- (lambda (record)
- (let ((score (or (bbdb-record-xfield record
bbdb/gnus-score-field)
- bbdb/gnus-score-default))
- (mail (bbdb-record-mail record)))
- (when (and score mail)
- (mapconcat
- (lambda (address)
- (format "(\"%s\" %s)\n" address score))
- mail ""))))
- (bbdb-records) "")
- "))"))))
- bbdb/gnus-score-alist)
-
-;;; from Brian Edmonds' gnus-bbdb.el
-;;
-;; Splitting / filing with gnus-folder
-;;
-;; To use this feature, you need to put this file somewhere in your
-;; load-path and add the following lines of code to your .gnus file:
-;;
-;; (setq nnmail-split-methods 'bbdb/gnus-split-method)
-;;
-;; You should also examine the variables defvar'd below and customize
-;; them to your taste. They're listed roughly in descending likelihood
-;; of your wanting to change them. Once that is done, you need to add
-;; filing information to your BBDB. There are two fields of interest:
-;;
-;; 1. gnus-private. This field contains the name of the group in which
-;; mail to you from any of the addresses associated with this record
-;; will be filed. Also, any self-copies of mail you send any of the
-;; same addresses will be filed here.
-;; 2. gnus-public. This field is used to keep mail from mailing lists
-;; out of the private mailboxes. It should be added to a record for
-;; the list submission address, and is formatted as follows:
-;; "group regexp"
-;; where group is where mail from the list should be filed, and
-;; regexp is a regular expression which is checked against the
-;; envelope sender (from the From_ header) to verify that this is
-;; the copy which came from the list. For example, the entry for
-;; the ding mailing list might be:
-;; "mail.emacs.ding address@hidden"
-;; Yes, the second part *is* a regexp, so those dots may match
-;; something other than dots. Sue me.
-;;
-;; Note that you can also specify a gnus-private field for mailing list
-;; addresses, in which case self-copies of mail you send to the list
-;; will be filed there. Also, the field names can be changed below if
-;; the defaults are not hip enough for you. Lastly, if you specify a
-;; gnus-private field for your *own* BBDB record, then all self-copies
-;; of mail you send will be filed to that group.
-;;
-;; This documentation should probably be expanded and moved to a
-;; separate file, but it's late, and *I* know what I'm trying to
-;; say. :)
-
-(defcustom bbdb/gnus-split-default-group "mail.misc"
- "If the BBDB does not indicate any group to spool a message to, it will
-be spooled to this group. If `bbdb/gnus-split-crosspost-default' is not
-nil, and if the BBDB did not indicate a specific group for one or more
-addresses, messages will be crossposted to this group in addition to any
-group(s) which the BBDB indicated."
- :group 'bbdb-mua-gnus-splitting
- :type 'string)
-
-(defcustom bbdb/gnus-split-nomatch-function nil
- "This function will be called after searching the BBDB if no place to
-file the message could be found. It should return a group name (or list
-of group names) -- `nnmail-split-fancy' as provided with Gnus is an
-excellent choice."
- :group 'bbdb-mua-gnus-splitting
- :type 'function)
-
-(defcustom bbdb/gnus-split-myaddr-regexp
- (concat "^" (user-login-name) "$\\|^"
- (user-login-name) "@\\([-a-z0-9]+\\.\\)*"
- (or (message-make-domain) (system-name) "") "$")
- "This regular expression should match your address as found in the
-From header of your mail."
- :group 'bbdb-mua-gnus-splitting
- :type 'regexp)
-
-(defcustom bbdb/gnus-split-crosspost-default nil
- "If this variable is not nil, then if the BBDB could not identify a
-group for every mail address, messages will be filed in
-`bbdb/gnus-split-default-group' in addition to any group(s) which the BBDB
-identified."
- :group 'bbdb-mua-gnus-splitting
- :type 'boolean)
-
-(defcustom bbdb/gnus-split-private-field 'gnus-private
- "This variable is used to determine the xfield to reference to find the
-associated group when saving private mail for a mail address known to
-the BBDB. The value of the xfield should be the name of a mail group."
- :group 'bbdb-mua-gnus-splitting
- :type 'symbol)
-
-(defcustom bbdb/gnus-split-public-field 'gnus-public
- "This variable is used to determine the xfield to reference to find the
-associated group when saving non-private mail (received from a mailing
-list) for a mail address known to the BBDB. The value of the xfield
-should be the name of a mail group, followed by a space, and a regular
-expression to match on the envelope sender to verify that this mail came
-from the list in question."
- :group 'bbdb-mua-gnus-splitting
- :type 'symbol)
-
-;; The split function works by assigning one of four spooling priorities
-;; to each group that is associated with an address in the message. The
-;; priorities are assigned as follows:
-;;
-;; 0. This priority is assigned when crosspost-default is nil to To/Cc
-;; addresses which have no private group defined in the BBDB. If the
-;; user's own address has no private group defined, then it will
-;; always be given this priority.
-;; 1. This priority is assigned to To/Cc addresses which have a private
-;; group defined in the BBDB. If crosspost-default is not nil, then
-;; To/Cc addresses which have no private group will also be assigned
-;; this priority. This is also assigned to the user's own address in
-;; the From position if a private group is defined for it.
-;; 2. This priority is assigned to From addresses which have a private
-;; group defined in the BBDB, except for the user's own address as
-;; described under priorities 0 and 1.
-;; 3. This priority is assigned to To/Cc addresses which have a public
-;; group defined in the BBDB, and whose associated regular expression
-;; matches the envelope sender (found in the header From_).
-;;
-;; The split function evaluates the spool priority for each address in
-;; the headers of the message, and returns as a list all the groups
-;; associated with the addresses which share the highest calculated
-;; priority.
-
-;;;###autoload
-(defun bbdb/gnus-split-method ()
- "This function expects to be called in a buffer which contains a mail
-message to be spooled, and the buffer should be narrowed to the message
-headers. It returns a list of groups to which the message should be
-spooled, using the addresses in the headers and information from BBDB."
- (let ((prq (list (list 0) (list 1) (list 2) (list 3))))
- ;; the From: header is special
- (let* ((hdr (or (mail-fetch-field "resent-from")
- (mail-fetch-field "from")
- (user-login-name)))
- (rv (bbdb/gnus-split-to-group hdr t)))
- (setcdr (nth (cdr rv) prq) (list (car rv))))
- ;; do the rest of the headers
- (let ((hdr (or (concat (or (mail-fetch-field "resent-to" nil t)
- (mail-fetch-field "to" nil t))
- ", "
- (mail-fetch-field "cc" nil t)
- ", "
- (mail-fetch-field "apparently-to" nil t))
- "")))
- (dolist (address (bbdb-extract-address-components hdr t))
- (let* ((rv (bbdb/gnus-split-to-group address))
- (pr (nth (cdr rv) prq)))
- (unless (member-ignore-case (car rv) pr)
- (setcdr pr (cons (car rv) (cdr pr)))))))
- ;; find the highest non-empty queue
- (setq prq (reverse prq))
- (while (and prq (not (cdr (car prq)))) (setq prq (cdr prq)))
- ;; and return...
- (if (not (or (not (cdr (car prq)))
- (and (equal (cdr (car prq)) (list
bbdb/gnus-split-default-group))
- (symbolp bbdb/gnus-split-nomatch-function)
- (fboundp bbdb/gnus-split-nomatch-function))))
- (cdr (car prq))
- (goto-char (point-min))
- (funcall bbdb/gnus-split-nomatch-function))))
-
-(defun bbdb/gnus-split-to-group (address &optional source)
- "This function is called from `bbdb/gnus-split-method' in order to
-determine the group and spooling priority for a single address."
- (condition-case nil
- (let* ((tmp (bbdb-extract-address-components address))
- (mail (cadr tmp))
- (record (car (bbdb-message-search (car tmp) mail)))
- public private rgx)
- (when record
- (setq private (bbdb-record-xfield record
bbdb/gnus-split-private-field)
- public (bbdb-record-xfield record
bbdb/gnus-split-public-field))
- (if (and public (not source) (string-match "^\\([^ ]+\\) \\(.*\\)$"
public))
- (setq rgx (substring public (match-beginning 2) (match-end 2))
- public (substring public (match-beginning 1) (match-end
1)))
- (setq public nil)))
- (cond
- ((and rgx public
- (goto-char (point-min))
- (re-search-forward "^From: \\([^ \n]+\\)[ \n]" nil t)
- (string-match rgx (buffer-substring (match-beginning 1)
- (match-end 1))))
- (cons public 3))
- (private
- (cons private
- (- 1 (if source -1 0)
- (if (string-match bbdb/gnus-split-myaddr-regexp mail) 1
0))))
- (t
- (cons bbdb/gnus-split-default-group
- (cond ((string-match bbdb/gnus-split-myaddr-regexp mail) 0)
- (source 2)
- (bbdb/gnus-split-crosspost-default 1)
- (t 0))))))
- (error (cons bbdb/gnus-split-default-group 0))))
-
-;;
-;; Imap support (Uwe Brauer)
-;;
-(defun bbdb/gnus-nnimap-folder-list-from-bbdb ()
- "Return a list of \( \"From\" mail-regexp imap-folder-name\) tuples
-based on the contents of the bbdb.
-
-The folder-name is the value of the 'imap attribute of the BBDB record;
-the mail-regexp consists of all the mail addresses for the BBDB record
-concatenated with OR. Records without an 'imap attribute are ignored.
-
-Here is an example of a relevant BBDB record:
-
-Uwe Brauer
- mail: address@hidden
- imap: testimap
-
-This function uses `regexp-opt' to generate the mail-regexp which automatically
-`regexp-quote's its arguments. Please note: in order that this will work
-with the `nnimap-split-fancy' method you have to use macros, that is your
setting
-will look like:
-
-\(setq nnimap-split-rule 'nnimap-split-fancy
- nnimap-split-inbox \"INBOX\"
- nnimap-split-fancy
- `\(| ,@\(bbdb/gnus-nnimap-folder-list-from-bbdb\)
- ... \)\)
-
-Note that `\( is the backquote, NOT the quote '\(."
-
- (let (;; the value of the 'imap attribute of a bbdb record
- folder-attr
- ;; a regexp matching all the mail addresses from a bbdb record
- mail-regexp
- ;; the list of (folder mail) tuples to return
- new-elmnt-list)
- ;; Loop over BBDB records. If an imap attribute exists for
- ;; the record, generate a regexp matching all the mail addresses
- ;; and add a tuple (folder mail-regexp) to the new-elmnt-list
- (dolist (record (bbdb-records))
- (when (setq folder-attr (bbdb-record-xfield record 'imap))
- (setq mail-regexp (regexp-opt (mapcar 'downcase
- (bbdb-record-mail record))))
- (unless (string= "" mail-regexp)
- (push (list "From" mail-regexp folder-attr)
- new-elmnt-list))))
- new-elmnt-list))
-
-;;
-;; Insinuation
-;;
-
-;;;###autoload
-(defun bbdb-insinuate-gnus ()
- "Hook BBDB into Gnus.
-Do not call this in your init file. Use `bbdb-initialize'."
- ;; `bbdb-mua-display-sender' fails in *Article* buffers, where
- ;; `gnus-article-read-summary-keys' provides an additional wrapper
- ;; that restores the window configuration.
- (define-key gnus-summary-mode-map ":" 'bbdb-mua-display-sender)
- (define-key gnus-article-mode-map ":" 'bbdb-mua-display-sender)
- ;; For `bbdb-mua-edit-field-sender' it is probably OK if
- ;;`gnus-article-read-summary-keys' restores the window configuration.
- (define-key gnus-summary-mode-map ";" 'bbdb-mua-edit-field-sender)
- (define-key gnus-article-mode-map ";" 'bbdb-mua-edit-field-sender)
- ;; Do we need keybindings for more commands? Suggestions welcome.
- ;; (define-key gnus-summary-mode-map ":" 'bbdb-mua-display-records)
- ;; (define-key gnus-summary-mode-map "'" 'bbdb-mua-display-recipients)
- ;; (define-key gnus-summary-mode-map ";" 'bbdb-mua-edit-field-recipients)
-
- ;; Set up user field for use in `gnus-summary-line-format'
- ;; (1) Big solution: use whole name
- (if bbdb-mua-summary-unify-format-letter
- (fset (intern (concat "gnus-user-format-function-"
- bbdb-mua-summary-unify-format-letter))
- (lambda (header)
- (bbdb-mua-summary-unify (mail-header-from header)))))
-
- ;; (2) Small solution: a mark for messages whos sender is in BBDB.
- (if bbdb-mua-summary-mark-format-letter
- (fset (intern (concat "gnus-user-format-function-"
- bbdb-mua-summary-mark-format-letter))
- (lambda (header)
- (bbdb-mua-summary-mark (mail-header-from header)))))
-
- ;; Scoring
- (add-hook 'bbdb-after-change-hook 'bbdb/gnus-score-invalidate-alist))
- ;; (setq gnus-score-find-score-files-function
- ;; (if (boundp 'gnus-score-find-score-files-function)
- ;; (cond ((functionp gnus-score-find-score-files-function)
- ;; (list gnus-score-find-score-files-function 'bbdb/gnus-score))
- ;; ((listp gnus-score-find-score-files-function)
- ;; (append gnus-score-find-score-files-function
'bbdb/gnus-score))
- ;; (t 'bbdb/gnus-score))
- ;; 'bbdb/gnus-score))
-
-(provide 'bbdb-gnus)
-
-;;; bbdb-gnus.el ends here
diff --git a/bbdb-sc.el b/bbdb-sc.el
deleted file mode 100644
index ada28ab..0000000
--- a/bbdb-sc.el
+++ /dev/null
@@ -1,196 +0,0 @@
-;;; bbdb-sc.el --- BBDB interface to Supercite -*- lexical-binding: t -*-
-
-;; Copyright (C) 1991, 1992 Jamie Zawinski <address@hidden>.
-;; Copyright (C) 2010-2017 Roland Winkler <address@hidden>
-
-;; This file is part of the Insidious Big Brother Database (aka BBDB),
-
-;; BBDB 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.
-
-;; BBDB 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 BBDB. If not, see <http://www.gnu.org/licenses/>.
-
-;;; Commentary:
-;; This file contains the BBDB interface to Supercite (sc)
-
-;; This file was written by Martin Sjolin <address@hidden>
-;; based on the original code by Tom Tromey <address@hidden>.
-;; Thanks to Richard Stanton <address@hidden> for ideas
-;; for improvements and to Michael D. Carney <address@hidden>
-;; for testing and feedback.
-
-;; This file adds the ability to define attributions for Supercite in BBDB
-;; and it enables you to retrieve your standard attribution from BBDB.
-;; If the From header in the mail message to which you are replying only
-;; contains the mail address, the sender's name is looked up in BBDB.
-;; The attribution is stored in the xfield `attribution' (unless you
-;; have changed `bbdb-sc-attribution-field').
-
-;; To enable supercite support for BBDB, call `bbdb-initialize' with arg `sc'.
-;; Also customize supercite as follows:
-;; (1) Add element "sc-consult" to `sc-preferred-attribution-list'
-;; (note that order matters!), e.g.,
-;;
-;; (setq sc-preferred-attribution-list
-;; '("sc-lastchoice" "x-attribution" "sc-consult"
-;; "initials" "firstname" "lastname"))
-;;
-;; (2) The variable `sc-attrib-selection-list' should include an element
-;;
-;; (add-to-list 'sc-attrib-selection-list
-;; '("from" ((".*" . (bbdb-sc-get-attrib
-;; (sc-mail-field "from"))))))
-;;
-;; (3) Set `sc-mail-glom-frame' as follows to fetch the sender's name from BBDB
-;; if there is only a plain mail address in the From field of the mail
message,
-;; e.g.,
-;;
-;; (setq sc-mail-glom-frame
-;; '((begin (setq sc-mail-headers-start (point)))
-;; ("^From " (sc-mail-check-from) nil nil)
-;; ("^x-attribution:[ \t]+.*$" (sc-mail-fetch-field t) nil t)
-;; ("^\\S +:.*$" (sc-mail-fetch-field) nil t)
-;; ("^$" (list 'abort '(step . 0)))
-;; ("^[ \t]+" (sc-mail-append-field))
-;; (sc-mail-warn-if-non-rfc822-p (sc-mail-error-in-mail-field))
-;; (end (progn
-;; (bbdb-sc-update-from)
-;; (setq sc-mail-headers-end
(point))))))
-
-;;; Code:
-
-(require 'bbdb-com)
-(require 'bbdb-mua)
-(require 'supercite)
-
-(defcustom bbdb-sc-attribution-field 'attribution
- "The BBDB xfield used for Supercite attribution."
- :group 'bbdb-utilities-sc
- :type '(symbol :tag "Field name"))
-(define-obsolete-variable-alias 'bbdb/sc-attribution-field
- 'bbdb-sc-attribution-field "3.0")
-
-(defcustom bbdb-sc-update-records-p 'search
- "How `bbdb-sc-set-attrib' updates BBDB records automatically.
-This may take the same values as arg UPDATE-P of `bbdb-update-records'."
- :group 'bbdb-utilities-sc
- :type '(choice (const :tag "do nothing" nil)
- (const :tag "search for existing records" search)
- (const :tag "update existing records" update)
- (const :tag "query annotation of all messages" query)
- (const :tag "annotate all messages" create)
- (function :tag "User-defined function")))
-
-(defcustom bbdb-sc-update-attrib-p 'query
- "How `bbdb-sc-set-attrib' updates the attribution field.
-Allowed values include
- nil Do not create or modify the attribution field
- query Query before creating or modifying the attribution field.
- t Create or modify the attribution field."
- :group 'bbdb-utilities-sc
- :type '(choice (const :tag "Do nothing" nil)
- (const :tag "Query before updating the attribution field"
query)
- (const :tag "Update the attribution field" t)))
-
-;;; Internal variables
-(defvar bbdb-sc-last-attrib ""
- "Last attribution used by Supercite.
-Used to compare against citation selected by the user.")
-
-(defun bbdb-sc-get-attrib (mail)
- "Get the Supercite attribution from BBDB.
-MAIL is the mail address to look for in BBDB."
- ;; We could store in `sc-mail-info' from which record we grabbed
- ;; this attribution. Yet we do not know whether `bbdb-sc-set-attrib'
- ;; will want to use the same record.
- (let* ((address (bbdb-extract-address-components mail))
- (record (bbdb-message-search (car address)
- (cadr address))))
- ;; FIXME: What to do if we have multiple matching records?
- (when (cdr record)
- (message "Multiple records match %s" mail)
- (sit-for 1))
- (if record
- (bbdb-record-field (car record) bbdb-sc-attribution-field))))
-(define-obsolete-function-alias 'bbdb/sc-consult-attr 'bbdb-sc-get-attrib
"3.0")
-
-(defun bbdb-sc-set-attrib ()
- "Store attribution in BBDB."
- (let ((from (bbdb-extract-address-components (sc-mail-field "from")))
- (attrib (sc-mail-field "sc-attribution"))
- bbdb-notice-mail-hook record)
- (when (and from attrib bbdb-sc-update-attrib-p
- (not (string-equal attrib bbdb-sc-last-attrib))
- (setq record (bbdb-update-records (list from)
- bbdb-sc-update-records-p)))
- ;; FIXME: What to do if we have multiple matching records?
- (when (cdr record)
- (message "Multiple records match %s" from)
- (sit-for 1))
- (setq record (car record))
- (let ((old (bbdb-record-field record bbdb-sc-attribution-field)))
- ;; Do nothing if the new value equals the old value
- (when (and (not (and old (string-equal old attrib)))
- (or (not (eq bbdb-sc-update-attrib-p 'query))
- (y-or-n-p (format (if (bbdb-record-field
- record bbdb-sc-attribution-field)
- "Change attribution for %s to %s?"
- "For %s add attribution %s?")
- (bbdb-record-name record) attrib))))
- (bbdb-record-set-field record bbdb-sc-attribution-field attrib)
- (bbdb-change-record record))))))
-(define-obsolete-function-alias 'bbdb/sc-set-attr 'bbdb-sc-set-attrib "3.0")
-
-;;;###autoload
-(defun bbdb-sc-update-from ()
- "Update the \"from\" field in `sc-mail-info'.
-If the \"from\" field in `sc-mail-info' contains only a plain mail address,
-complement the \"from\" field in `sc-mail-info' with the sender's name in
BBDB."
- (let* ((from (sc-mail-field "from"))
- ;; Do not use `bbdb-extract-address-components' that can "invent"
names.
- (address (and from (bbdb-decompose-bbdb-address from)))
- ;; FIXME: Should we always update the sender's name in `sc-mail-info'
- ;; if it does not agree with what BBDB says?
- (record (if (and (cadr address) (not (car address)))
- (bbdb-message-search nil (cadr address))))
- ;; FIXME: What to do if we have multiple matching records?
- (_ (when (cdr record)
- (message "Multiple records match %s" from)
- (sit-for 1)))
- (name (and record (bbdb-record-name (car record)))))
- (if name
- (setcdr (assoc-string "from" sc-mail-info t)
- (format "%s <%s>" name (cadr address))))))
-(define-obsolete-function-alias 'bbdb/sc-default 'bbdb-sc-update-from "3.0")
-
-;; Insert our hooks
-
-;; Dammit, supercite! It runs `sc-attribs-postselect-hook' in an
-;; environment with the local variable `attribution' that we rely on.
-(with-no-warnings (defvar attribution))
-
-;;;###autoload
-(defun bbdb-insinuate-sc ()
- "Hook BBDB into Supercite.
-Do not call this in your init file. Use `bbdb-initialize'.
-However, this is not the full story. See bbdb-sc.el for how to fully hook
-BBDB into Supercite."
- (add-hook 'sc-post-hook 'bbdb-sc-set-attrib)
- (add-hook 'sc-attribs-postselect-hook
- (lambda ()
- (setq bbdb-sc-last-attrib
- (if sc-downcase-p
- (downcase attribution)
- attribution)))))
-
-(provide 'bbdb-sc)
-
-;;; bbdb-sc.el ends here
diff --git a/bbdb-vm.el b/bbdb-vm.el
deleted file mode 100644
index 023ff7c..0000000
--- a/bbdb-vm.el
+++ /dev/null
@@ -1,344 +0,0 @@
-;;; bbdb-vm.el --- BBDB interface to VM -*- lexical-binding: t -*-
-
-;; Copyright (C) 1991, 1992, 1993 Jamie Zawinski <address@hidden>.
-;; Copyright (C) 2010-2017 Roland Winkler <address@hidden>
-
-;; This file is part of the Insidious Big Brother Database (aka BBDB),
-
-;; BBDB 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.
-
-;; BBDB 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 BBDB. If not, see <http://www.gnu.org/licenses/>.
-
-;;; Commentary:
-;; This file contains the BBDB interface to VM.
-;; See the BBDB info manual for documentation.
-
-;;; Code:
-
-(require 'bbdb)
-(require 'bbdb-com)
-(require 'bbdb-mua)
-(when t ;Only load at run-time, not during compilation
- (require 'vm-autoloads)
- (require 'vm)
- (require 'vm-motion)
- (require 'vm-summary)
- (require 'vm-mime)
- (require 'vm-vars)
- (require 'vm-macro)
- (require 'vm-message)
- (require 'vm-misc))
-
-;; Since VM is not loaded during compilation (e.g. because it may not be
-;; available during compilation), we need the declarations below to
-;; silence the byte-compiler warnings.
-(defvar vm-message-pointer)
-(defvar vm-summary-uninteresting-senders)
-(defvar vm-summary-uninteresting-senders-arrow)
-(defvar vm-auto-folder-alist)
-(defvar vm-folder-directory)
-(defvar vm-primary-inbox)
-(defvar vm-virtual-folder-alist)
-(defvar vm-mode-map)
-(declare-function vm-get-header-contents "??")
-(declare-function vm-su-from "??")
-(declare-function vm-su-to "??")
-(declare-function vm-decode-mime-encoded-words-in-string "??")
-(declare-function vm-su-to-names "??")
-(declare-function vm-su-full-name "??")
-(declare-function vm-add-message-labels "??")
-(declare-function vm-su-interesting-full-name "??")
-(declare-function vm-select-folder-buffer "??")
-
-(defun bbdb/vm-header (header)
- (save-current-buffer
- (vm-select-folder-buffer)
- (vm-get-header-contents (car vm-message-pointer)
- (concat header ":"))))
-
-
-;; By Alastair Burt <address@hidden>
-;; vm 5.40 and newer support a new summary format, %U<letter>, to call
-;; a user-provided function. Use "%-17.17UB" instead of "%-17.17F" to
-;; have your VM summary buffers display BBDB's idea of the sender's full
-;; name instead of the name (or lack thereof) in the message itself.
-
-;; RW: this is a VM-specific version of `bbdb-mua-summary-unify'
-;; which respects `vm-summary-uninteresting-senders'.
-
-(defun vm-summary-function-B (m)
- "For VM message M return the BBDB name of the sender.
-Respect `vm-summary-uninteresting-senders'."
- (if vm-summary-uninteresting-senders
- (if (let ((case-fold-search t))
- (string-match vm-summary-uninteresting-senders (vm-su-from m)))
- (concat vm-summary-uninteresting-senders-arrow
- (or (bbdb/vm-alternate-full-name (vm-su-to m))
- (vm-decode-mime-encoded-words-in-string
- (vm-su-to-names m))))
- (or (bbdb/vm-alternate-full-name (vm-su-from m))
- (vm-su-full-name m)))
- (or (bbdb/vm-alternate-full-name (vm-su-from m))
- (vm-decode-mime-encoded-words-in-string (vm-su-full-name m)))))
-
-(defun bbdb/vm-alternate-full-name (address)
- (if address
- (let* ((data (bbdb-extract-address-components address))
- (record (car (bbdb-message-search (car data) (cadr data)))))
- (if record
- (or (bbdb-record-xfield record 'mail-name)
- (bbdb-record-name record))))))
-
-
-
-;;;###autoload
-(defcustom bbdb/vm-auto-folder-headers '("From:" "To:" "CC:")
- "The headers used by `bbdb/vm-auto-folder'.
-The order in this list is the order how matching will be performed."
- :group 'bbdb-mua-vm
- :type '(repeat (string :tag "header name")))
-
-;;;###autoload
-(defcustom bbdb/vm-auto-folder-field 'vm-folder
- "The xfield which `bbdb/vm-auto-folder' searches for."
- :group 'bbdb-mua-vm
- :type 'symbol)
-
-;;;###autoload
-(defcustom bbdb/vm-virtual-folder-field 'vm-virtual
- "The xfield which `bbdb/vm-virtual-folder' searches for."
- :group 'bbdb-mua-vm
- :type 'symbol)
-
-;;;###autoload
-(defcustom bbdb/vm-virtual-real-folders nil
- "Real folders used for defining virtual folders.
-If nil use `vm-primary-inbox'."
- :group 'bbdb-mua-vm
- :type '(choice (const :tag "Use vm-primary-inbox" nil)
- (repeat (string :tag "Real folder"))))
-
-;;;###autoload
-(defun bbdb/vm-auto-folder ()
- "Add entries to `vm-auto-folder-alist' for the records in BBDB.
-For each record that has a `vm-folder' xfield, add an element
-\(MAIL-REGEXP . FOLDER-NAME) to `vm-auto-folder-alist'.
-The element gets added to the sublists of `vm-auto-folder-alist'
-specified in `bbdb/vm-auto-folder-headers'.
-MAIL-REGEXP matches the mail addresses of the BBDB record.
-The value of the `vm-folder' xfield becomes FOLDER-NAME.
-The `vm-folder' xfield is defined via `bbdb/vm-auto-folder-field'.
-
-Add this function to `bbdb-before-save-hook' and your .vm."
- (interactive)
- (let ((records ; Collect BBDB records with a vm-folder xfield.
- (delq nil
- (mapcar (lambda (r)
- (if (bbdb-record-xfield r bbdb/vm-auto-folder-field)
- r))
- (bbdb-records))))
- folder-list folder-name mail-regexp)
- ;; Add (MAIL-REGEXP . FOLDER-NAME) pair to this sublist of
`vm-auto-folder-alist'
- (dolist (header bbdb/vm-auto-folder-headers)
- ;; create the folder-list in `vm-auto-folder-alist' if it does not exist
- (unless (setq folder-list (assoc header vm-auto-folder-alist))
- (push (list header) vm-auto-folder-alist)
- (setq folder-list (assoc header vm-auto-folder-alist)))
- (dolist (record records)
- ;; Ignore everything past a comma
- (setq folder-name (car (bbdb-record-xfield-split
- record bbdb/vm-auto-folder-field))
- ;; quote all the mail addresses for the record and join them
- mail-regexp (regexp-opt (bbdb-record-mail record)))
- ;; In general, the values of xfields are strings (required for
editing).
- ;; If we could set the value of `bbdb/vm-auto-folder-field' to a
symbol,
- ;; it could be a function that is called with arg record to calculate
- ;; the value of folder-name.
- ;; (if (functionp folder-name)
- ;; (setq folder-name (funcall folder-name record)))
- (unless (or (string= "" mail-regexp)
- (assoc mail-regexp folder-list))
- ;; Convert relative into absolute file names using
- ;; `vm-folder-directory'.
- (unless (file-name-absolute-p folder-name)
- (setq folder-name (abbreviate-file-name
- (expand-file-name folder-name
- vm-folder-directory))))
- ;; nconc modifies the list in place
- (nconc folder-list (list (cons mail-regexp folder-name))))))))
-
-;;;###autoload
-(defun bbdb/vm-virtual-folder ()
- "Create `vm-virtual-folder-alist' according to the records in BBDB.
-For each record that has a `vm-virtual' xfield, add or modify the
-corresponding VIRTUAL-FOLDER-NAME element of `vm-virtual-folder-alist'.
-
- (VIRTUAL-FOLDER-NAME ((FOLDER-NAME ...)
- (author-or-recipient MAIL-REGEXP)))
-
-VIRTUAL-FOLDER-NAME is the first element of the `vm-virtual' xfield.
-FOLDER-NAME ... are either the remaining elements of the `vm-virtual' xfield,
-or `bbdb/vm-virtual-real-folders' or `vm-primary-inbox'.
-MAIL-REGEXP matches the mail addresses of the BBDB record.
-The `vm-virtual' xfield is defined via `bbdb/vm-virtual-folder-field'.
-
-Add this function to `bbdb-before-save-hook' and your .vm."
- (interactive)
- (let (real-folders mail-regexp folder val tmp)
- (dolist (record (bbdb-records))
- (when (setq val (bbdb-record-xfield-split
- record bbdb/vm-virtual-folder-field))
- (setq mail-regexp (regexp-opt (bbdb-record-mail record)))
- (unless (string= "" mail-regexp)
- (setq folder (car val)
- real-folders (mapcar
- (lambda (f)
- (if (file-name-absolute-p f) f
- (abbreviate-file-name
- (expand-file-name f vm-folder-directory))))
- (or (cdr val) bbdb/vm-virtual-real-folders
- (list vm-primary-inbox)))
- ;; Either extend the definition of an already defined
- ;; virtual folder or define a new virtual folder
- tmp (or (assoc folder vm-virtual-folder-alist)
- (car (push (list folder) vm-virtual-folder-alist)))
- tmp (or (assoc real-folders (cdr tmp))
- (car (setcdr tmp (cons (list real-folders)
- (cdr tmp)))))
- tmp (or (assoc 'author-or-recipient (cdr tmp))
- (car (setcdr tmp (cons (list 'author-or-recipient)
- (cdr tmp))))))
- (cond ((not (cdr tmp))
- (setcdr tmp (list mail-regexp)))
- ((not (string-match (regexp-quote mail-regexp)
- (cadr tmp)))
- (setcdr tmp (list (concat (cadr tmp) "\\|"
mail-regexp))))))))))
-
-
-;; RW: Adding custom labels to VM messages allows one to create,
-;; for example, virtual folders. The following code creates
-;; the required labels in a rather simplistic way, checking merely
-;; whether the sender's BBDB record uses a certain mail alias.
-;; (Note that `bbdb/vm-virtual-folder' can achieve the same goal,
-;; yet this requires a second xfield that must be kept up-to-date, too.)
-;; To make auto labels yet more useful, the code could allow more
-;; sophisticated schemes, too. Are there real-world applications
-;; for this?
-
-;;; Howard Melman, contributed Jun 16 2000
-(defcustom bbdb/vm-auto-add-label-list nil
- "List used by `bbdb/vm-auto-add-label' to automatically label VM messages.
-Its elements may be strings used both as the xfield value to check for
-and as the label to apply to the message.
-If an element is a cons pair (VALUE . LABEL), VALUE is the xfield value
-to search for and LABEL is the label to apply."
- :group 'bbdb-mua-vm
- :type 'list)
-
-(defcustom bbdb/vm-auto-add-label-field bbdb-mail-alias-field
- "Xfields used by `bbdb/vm-auto-add-label' to automatically label messages.
-This is either a single BBDB xfield or a list of xfields that
-`bbdb/vm-auto-add-label' uses to check for labels to apply to a message.
-Defaults to `bbdb-mail-alias-field' which defaults to `mail-alias'."
- :group 'bbdb-mua-vm
- :type '(choice symbol list))
-
-(defun bbdb/vm-auto-add-label (record)
- "Automatically add labels to VM messages.
-Add this to `bbdb-notice-record-hook' to check the messages noticed by BBDB.
-If the value of `bbdb/vm-auto-add-label-field' in the sender's BBDB record
-matches a value in `bbdb/vm-auto-add-label-list' then a VM label will be added
-to the message. Such VM labels can be used, e.g., to mark messages via
-`vm-mark-matching-messages' or to define virtual folders via
-`vm-create-virtual-folder'
-
-Typically `bbdb/vm-auto-add-label-field' and `bbdb/vm-auto-add-label-list'
-refer to mail aliases FOO used with multiple records. This adds a label FOO
-to all incoming messages matching FOO. Then VM can create a virtual folder
-for these messages. The concept of combining multiple recipients of an
-outgoing message in one mail alias thus gets extended to incoming messages
-from different senders."
- ;; This could go into `vm-arrived-message-hook' to check messages only once.
- (if (eq major-mode 'vm-mode)
- (let* ((xvalues
- ;; Inspect the relevant fields of RECORD
- (append
- (mapcar (lambda (field)
- (bbdb-record-xfield-split record field))
- (cond ((listp bbdb/vm-auto-add-label-field)
- bbdb/vm-auto-add-label-field)
- ((symbolp bbdb/vm-auto-add-label-field)
- (list bbdb/vm-auto-add-label-field))
- (t (error "Bad value for
bbdb/vm-auto-add-label-field"))))))
- ;; Collect the relevant labels from `bbdb/vm-auto-add-label-list'
- (labels
- (delq nil
- (mapcar (lambda (l)
- (cond ((stringp l)
- (if (member l xvalues)
- l))
- ((and (consp l)
- (stringp (car l))
- (stringp (cdr l)))
- (if (member (car l) xvalues)
- (cdr l)))
- (t
- (error "Malformed
bbdb/vm-auto-add-label-list"))))
- bbdb/vm-auto-add-label-list))))
- (if labels
- (vm-add-message-labels
- (mapconcat 'identity labels " ") 1)))))
-
-
-
-;;;###autoload
-(defun bbdb-insinuate-vm ()
- "Hook BBDB into VM.
-Do not call this in your init file. Use `bbdb-initialize'."
- (define-key vm-mode-map ":" 'bbdb-mua-display-records)
- (define-key vm-mode-map "`" 'bbdb-mua-display-sender)
- (define-key vm-mode-map "'" 'bbdb-mua-display-recipients)
- (define-key vm-mode-map ";" 'bbdb-mua-edit-field-sender)
- ;; Do we need keybindings for more commands? Suggestions welcome.
- ;; (define-key vm-mode-map "'" 'bbdb-mua-edit-field-recipients)
- (define-key vm-mode-map "/" 'bbdb)
- ;; `mail-mode-map' is the parent of `vm-mail-mode-map'.
- ;; So the following is also done by `bbdb-insinuate-mail'.
- (if (and bbdb-complete-mail (boundp 'vm-mail-mode-map))
- (define-key vm-mail-mode-map "\M-\t" 'bbdb-complete-mail))
-
- ;; Set up user field for use in `vm-summary-format'
- ;; (1) Big solution: use whole name
- (if bbdb-mua-summary-unify-format-letter
- (fset (intern (concat "vm-summary-function-"
- bbdb-mua-summary-unify-format-letter))
- (lambda (m) (bbdb-mua-summary-unify
- ;; VM does not give us the original From header.
- ;; So we have to work backwards.
- (let ((name (vm-decode-mime-encoded-words-in-string
- (vm-su-interesting-full-name m)))
- (mail (vm-su-from m)))
- (if (string= name mail) mail
- (format "\"%s\" <%s>" name mail)))))))
-
- ;; (2) Small solution: a mark for messages whos sender is in BBDB.
- (if bbdb-mua-summary-mark-format-letter
- (fset (intern (concat "vm-summary-function-"
- bbdb-mua-summary-mark-format-letter))
- ;; VM does not give us the original From header.
- ;; So we assume that the mail address is sufficient to identify
- ;; the BBDB record of the sender.
- (lambda (m) (bbdb-mua-summary-mark (vm-su-from m))))))
-
-(provide 'bbdb-vm)
-
-;;; bbdb-vm.el ends here
diff --git a/bbdb.el b/bbdb.el
index ccfc869..c014f33 100644
--- a/bbdb.el
+++ b/bbdb.el
@@ -3,7 +3,7 @@
;; Copyright (C) 1991, 1992, 1993, 1994 Jamie Zawinski <address@hidden>.
;; Copyright (C) 2010-2017 Roland Winkler <address@hidden>
-;; Version: 3.0
+;; Version: 0
;; Package-Requires: ((emacs "24"))
;; This file is part of the Insidious Big Brother Database (aka BBDB),
diff --git a/bbdb.info b/bbdb.info
new file mode 100644
index 0000000..22bf44f
--- /dev/null
+++ b/bbdb.info
@@ -0,0 +1,1283 @@
+This is bbdb.info, produced by makeinfo version 6.5 from bbdb.texi.
+
+This file documents the Insidious Big Brother Database (BBDB)
+
+ Copyright (C) 2011-2017 Roland Winkler <address@hidden>
+
+ 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 the Invariant Section being "GNU GENERAL PUBLIC
+ LICENSE," A copy of the license is included in the section entitled
+ "GNU Free Documentation License."
+INFO-DIR-SECTION Emacs misc features
+START-INFO-DIR-ENTRY
+* BBDB: (bbdb). Insidious Big Brother Database (BBDB).
+END-INFO-DIR-ENTRY
+
+
+File: bbdb.info, Node: Top, Next: First Chapter, Prev: (dir), Up: (dir)
+
+BBDB User Manual
+****************
+
+This file documents the Insidious Big Brother Database (BBDB)
+
+ Copyright (C) 2011-2017 Roland Winkler <address@hidden>
+
+ 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 the Invariant Section being "GNU GENERAL PUBLIC
+ LICENSE," A copy of the license is included in the section entitled
+ "GNU Free Documentation License."
+
+* Menu:
+
+* First Chapter:: The first chapter is the only chapter
+ in this sample.
+
+Appendices
+* Copying:: The GNU General Public License gives you
permission
+ to redistribute GNU Emacs on certain terms;
+ it also explains that there is no warranty.
+* GNU Free Documentation License:: The license for this documentation.
+* Index:: Complete index.
+
+
+
+
+
+File: bbdb.info, Node: First Chapter, Next: Copying, Prev: Top, Up: Top
+
+1 First Chapter
+***************
+
+This is the first chapter.
+
+ Here is a numbered list.
+
+ 1. This is the first item.
+
+ 2. This is the second item.
+
+
+File: bbdb.info, Node: Copying, Next: GNU Free Documentation License, Prev:
First Chapter, Up: Top
+
+Appendix A GNU GENERAL PUBLIC LICENSE
+*************************************
+
+ 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: bbdb.info, Node: GNU Free Documentation License, Next: Index, Prev:
Copying, Up: Top
+
+Appendix B GNU Free Documentation License
+*****************************************
+
+ 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: bbdb.info, Node: Index, Prev: GNU Free Documentation License, Up: Top
+
+Index
+*****
+
+ [index ]
+* Menu:
+
+* chapter, first: First Chapter. (line 6)
+* index entry, another: First Chapter. (line 6)
+
+
+
+Tag Table:
+Node: Top728
+Node: First Chapter1831
+Node: Copying2061
+Node: GNU Free Documentation License39627
+Node: Index64773
+
+End Tag Table
diff --git a/dir b/dir
new file mode 100644
index 0000000..9492a22
--- /dev/null
+++ b/dir
@@ -0,0 +1,20 @@
+Ceci est le fichier .../info/dir, qui contient le nœud le
+plus haut de la hiérarchie Info. Ce nœud est appelé (dir)Top.
+C'est de ce nœud que vous démarrez la première fois que
+vous utilisez Info.
+
+File: dir, Node: Top Ceci est le haut de l'arborescence INFO
+
+ Ceci (le nœud Répertoire) fournit un menu des sujets majeurs.
+ Entrez « q » pour quitter, « H » pour afficher toutes les commandes Info,
+ « d » pour revenir ici ;, « h » affiche un guide d'initiation pour les
+ nouveaux venus.
+ « mEmacs<Entrée> » démarre une consultation du manuel Emacs, et cætera.
+
+ Dans Emacs, vous pouvez cliquer avec le deuxième bouton de la souris
+ sur une entrée de menu ou sur un renvoi pour le sélectionner.
+
+* Menu:
+
+Emacs misc features
+* BBDB: (bbdb). Insidious Big Brother Database (BBDB).
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] scratch/bbdb 251d2d1: Remove files with unclear copyright status; prepare for move to externals/,
Stefan Monnier <=