[elpa] master b11eef7: Add mail command index in debbugs

2018-11-02 Thread Michael Albinus
branch: master
commit b11eef7c968e4dd66be228a7d9ad3a76544b4e0b
Author: Michael Albinus 
Commit: Michael Albinus 

Add mail command index in debbugs

* packages/debbugs/debbugs-ug.texi (Top): Add Mail Command Index.

* packages/debbugs/debbugs.texi (Requesting bug numbers)
(Searching bugs): Use @uref{}.

* packages/debbugs/instructions.texi: New file.
---
 packages/debbugs/debbugs-ug.info   | 332 +++--
 packages/debbugs/debbugs-ug.texi   |   6 +
 packages/debbugs/debbugs.texi  |   4 +-
 packages/debbugs/instructions.texi | 302 +
 4 files changed, 628 insertions(+), 16 deletions(-)

diff --git a/packages/debbugs/debbugs-ug.info b/packages/debbugs/debbugs-ug.info
index 7e3901d..19d7040 100644
--- a/packages/debbugs/debbugs-ug.info
+++ b/packages/debbugs/debbugs-ug.info
@@ -57,6 +57,7 @@ Org Mode: (org)Top.).  As backend they use the 'debbugs' 
Emacs library
 * Command Index::   Debbugs commands.
 * Variable Index::  User options and variables.
 * Key Index::   Keyboard strokes on bug report buffers.
+* Mail Command Index::  Debbugs control mailserver commands.
 
 
 File: debbugs-ug.info,  Node: Retrieving Bugs,  Next: Searching Bugs,  Prev: 
Top,  Up: Top
@@ -641,7 +642,7 @@ Variable Index
 * debbugs-org-severity-priority: TODO Items.(line  10)
 
 
-File: debbugs-ug.info,  Node: Key Index,  Prev: Variable Index,  Up: Top
+File: debbugs-ug.info,  Node: Key Index,  Next: Mail Command Index,  Prev: 
Variable Index,  Up: Top
 
 Key Index
 *
@@ -670,22 +671,325 @@ Key Index
 * w: Tabulated Lists.(line 49)
 * x: Tabulated Lists.(line 68)
 
+
+File: debbugs-ug.info,  Node: Mail Command Index,  Prev: Key Index,  Up: Top
+
+Debbugs control mailserver commands
+***
+
+'reassign bugnumber package [ version ]'
+ Records that bug #bugnumber is a bug in package.  This can be
+ used to set the package if the user forgot the pseudo-header, or
+ to change an earlier assignment.  No notifications are sent to
+ anyone (other than the usual information in the processing
+ transcript).
+
+ If you supply a version, the bug tracking system will note that
+ the bug affects that version of the newly-assigned package.
+
+'reopen bugnumber [ originator-address | = | ! ]'
+ Reopens #bugnumber if it is closed.
+
+ By default, or if you specify =, the original submitter is still
+ as the originator of the report, so that they will get the ack
+ when it is closed again.
+
+ If you supply an originator-address the originator will be set to
+ the address you supply.  If you wish to become the new originator
+ of the reopened report you can use the !  shorthand or specify
+ your own email address.
+
+ It is usually a good idea to tell the person who is about to be
+ recorded as the originator that you're reopening the report, so
+ that they will know to expect the ack which they'll get when it
+ is closed again.
+
+ If the bug is not closed then reopen won't do anything, not even
+ change the originator.  To change the originator of an open bug
+ report, use the submitter command; note that this will inform the
+ original submitter of the change.
+
+ If the bug was recorded as being closed in a particular version
+ of a package but recurred in a later version, it is better to use
+ the found command instead.
+
+'found bugnumber [ version ]'
+ Record that #bugnumber has been encountered in the given version
+ of the package to which it is assigned.
+
+ The bug tracking system uses this information, in conjunction
+ with fixed versions recorded when closing bugs, to display lists
+ of bugs open in various versions of each package.  It considers a
+ bug to be open when it has no fixed version, or when it has been
+ found more recently than it has been fixed.
+
+ If no version is given, then the list of fixed versions for the
+ bug is cleared.  This is identical to the behaviour of reopen.
+
+ This command will only cause a bug to be marked as not done if no
+ version is specified, or if the version being marked found is
+ equal to the version which was last marked fixed.  (If you are
+ certain that you want the bug marked as not done, use reopen in
+ conjunction with found.
+
+ This command was introduced in preference to reopen because it
+ was difficult to add a version to that command's syntax without
+ suffering ambiguity.
+
+'notfound bugnumber version'
+ Remove the record that #bugnumber was encountered in the given
+ version of the package to which it is assigned.
+
+ This differs from closing the bug at that version in that the bug
+ is not listed as fixed in that version

[elpa] master 6941464: * packages/debbugs/instructions.texi: Add @anchor{}.

2018-11-02 Thread Michael Albinus
branch: master
commit 6941464ab7401a54e96d36f165f8cfe48ce78c3b
Author: Michael Albinus 
Commit: Michael Albinus 

* packages/debbugs/instructions.texi: Add @anchor{}.
---
 packages/debbugs/debbugs-ug.info   | 30 ++
 packages/debbugs/instructions.texi | 44 --
 2 files changed, 67 insertions(+), 7 deletions(-)

diff --git a/packages/debbugs/debbugs-ug.info b/packages/debbugs/debbugs-ug.info
index 19d7040..6e45558 100644
--- a/packages/debbugs/debbugs-ug.info
+++ b/packages/debbugs/debbugs-ug.info
@@ -991,5 +991,35 @@ Node: Command Index22342
 Node: Variable Index23131
 Node: Key Index24205
 Node: Mail Command Index25771
+Ref: Mail Command Index: reassign25924
+Ref: Mail Command Index: reopen26388
+Ref: Mail Command Index: found27542
+Ref: Mail Command Index: notfound28623
+Ref: Mail Command Index: submitter29032
+Ref: Mail Command Index: forwarded29426
+Ref: Mail Command Index: notforwarded29765
+Ref: Mail Command Index: retitle29966
+Ref: Mail Command Index: severity30350
+Ref: Mail Command Index: clone30615
+Ref: Mail Command Index: merge31379
+Ref: Mail Command Index: forcemerge32766
+Ref: Mail Command Index: unmerge33040
+Ref: Mail Command Index: tags33743
+Ref: Mail Command Index: block34850
+Ref: Mail Command Index: unblock34892
+Ref: Mail Command Index: close35382
+Ref: Mail Command Index: package36032
+Ref: Mail Command Index: owner36644
+Ref: Mail Command Index: noowner37007
+Ref: Mail Command Index: archive37180
+Ref: Mail Command Index: unarchive37321
+Ref: Mail Command Index: #37614
+Ref: Mail Command Index: quit37874
+Ref: Mail Command Index: stop37881
+Ref: Mail Command Index: thank37888
+Ref: Mail Command Index: thanks37896
+Ref: Mail Command Index: thankyou37905
+Ref: Mail Command Index: thank you37916
+Ref: Mail Command Index: --37928
 
 End Tag Table
diff --git a/packages/debbugs/instructions.texi 
b/packages/debbugs/instructions.texi
index e3c5f29..ba51807 100644
--- a/packages/debbugs/instructions.texi
+++ b/packages/debbugs/instructions.texi
@@ -1,4 +1,5 @@
 @table @samp
+@anchor{Mail Command Index: reassign}
 @item reassign bugnumber package [ version ]
 Records that bug #bugnumber is a bug in package. This can be used
 to set the package if the user forgot the pseudo-header, or to
@@ -8,6 +9,7 @@ change an earlier assignment. No notifications are sent to 
anyone
 If you supply a version, the bug tracking system will note that
 the bug affects that version of the newly-assigned package.
 
+@anchor{Mail Command Index: reopen}
 @item reopen bugnumber [ originator-address | = | ! ]
 Reopens #bugnumber if it is closed.
 
@@ -34,6 +36,7 @@ If the bug was recorded as being closed in a particular 
version of
 a package but recurred in a later version, it is better to use the
 found command instead.
 
+@anchor{Mail Command Index: found}
 @item found bugnumber [ version ]
 Record that #bugnumber has been encountered in the given version
 of the package to which it is assigned.
@@ -57,6 +60,7 @@ This command was introduced in preference to reopen because 
it was
 difficult to add a version to that command's syntax without
 suffering ambiguity.
 
+@anchor{Mail Command Index: notfound}
 @item notfound bugnumber version
 Remove the record that #bugnumber was encountered in the given
 version of the package to which it is assigned.
@@ -66,6 +70,7 @@ is not listed as fixed in that version either; no information
 about that version will be known. It is intended for fixing
 mistakes in the record of when a bug was found.
 
+@anchor{Mail Command Index: submitter}
 @item submitter bugnumber originator-address | !
 Changes the originator of #bugnumber to originator-address.
 
@@ -76,6 +81,7 @@ While the reopen command changes the originator of other bugs
 merged with the one being reopened, submitter does not affect
 merged bugs.
 
+@anchor{Mail Command Index: forwarded}
 @item forwarded bugnumber address
 Notes that bugnumber has been forwarded to the upstream maintainer
 at address. This does not actually forward the report. This can be
@@ -83,11 +89,13 @@ used to change an existing incorrect forwarded-to address, 
or to
 record a new one for a bug that wasn't previously noted as having
 been forwarded.
 
+@anchor{Mail Command Index: notforwarded}
 @item notforwarded bugnumber
 Forgets any idea that bugnumber has been forwarded to any upstream
 maintainer. If the bug was not recorded as having been forwarded
 then this will do nothing.
 
+@anchor{Mail Command Index: retitle}
 @item retitle bugnumber new-title
 Changes the title of a bug report to that specified (the default
 is the Subject mail header from the original report).
@@ -97,6 +105,7 @@ one of a set of merged reports this will change the title of 
only
 the individual bug requested, and not all those with which it is
 merged.
 
+@anchor{Mail Command Index: severity}
 @item severity bugnumber severity
 Set the severity level for bug report #bugnumb

[elpa] externals/zones 16ea023: * zones.el: Improve the doc. Mention it's on GNU ELPA

2018-11-02 Thread Stefan Monnier
branch: externals/zones
commit 16ea0232f24b326dc6fb975db9d628bf39ecc968
Author: Drew Adams 
Commit: Stefan Monnier 

* zones.el: Improve the doc.  Mention it's on GNU ELPA

(narrow-map): Don't override pre-existing bindings.
---
 zones.el | 204 +++
 1 file changed, 140 insertions(+), 64 deletions(-)

diff --git a/zones.el b/zones.el
index 1140d81..8569488 100644
--- a/zones.el
+++ b/zones.el
@@ -7,11 +7,12 @@
 ;; Author: Drew Adams
 ;; Maintainer: Drew Adams 
 ;; Created: Sun Apr 18 12:58:07 2010 (-0700)
-;; Version: 2018.10.28
+;; Version: 2018.11.01
 ;; Package-Requires: ()
-;; Last-Updated: Tue Oct 30 13:07:40 2018 (-0700)
+;; Last-Updated: Thu Nov  1 09:46:25 2018 (-0700)
 ;;   By: dradams
-;; Update #: 2152
+;; Update #: 2236
+;; URL: https://elpa.gnu.org/packages/zones.html
 ;; URL: https://www.emacswiki.org/emacs/download/zones.el
 ;; Doc URL: https://www.emacswiki.org/emacs/Zones
 ;; Doc URL: https://www.emacswiki.org/emacs/MultipleNarrowings
@@ -20,7 +21,8 @@
 ;;
 ;; Features that might be required by this library:
 ;;
-;;   `backquote', `bytecomp', `cconv', `cl-lib', `macroexp'.
+;;   `backquote', `bytecomp', `cconv', `cl', `cl-lib', `gv',
+;;   `macroexp'.
 ;;
 ;;
 ;;
@@ -28,10 +30,17 @@
 ;;
 ;; Zones of text - like multiple regions.
 ;;
-;;More description below.
-;;
 ;;Bug reports etc.: (concat "drew" ".adams" "@" "oracle" ".com")
 ;;
+;;You can get `zones.el' from Emacs Wiki or GNU ELPA:
+;;
+;;* Emacs Wiki: https://www.emacswiki.org/emacs/download/zones.el
+;;* GNU ELPA:   https://elpa.gnu.org/packages/zones.html
+;;
+;;The instance on Emacs Wiki might sometimes be more recent, but
+;;major changes (named ''versions'') are posted to GNU ELPA.
+;;
+;;More description below.
 
 ;;(@> "Index")
 ;;
@@ -48,7 +57,9 @@
 ;;  (@> "Things Defined Here")
 ;;  (@> "Documentation")
 ;;(@> "Compatibility")
+;;(@> "Zones")
 ;;(@> "Coalesced (United) Zones")
+;;(@> "Noncontiguous Region and Set of Zones")
 ;;(@> "Zones and Overlays")
 ;;(@> "Izone Commands")
 ;;(@> "Izone List Variables")
@@ -170,6 +181,7 @@
 ;;  BUFFER is a buffer name (string) and where POSITION is a buffer
 ;;  position (number only).
 ;;
+;;  The content of a zone is any contiguous stretch of buffer text.
 ;;  The positions of a zone can be in either numeric order.  The
 ;;  positions are also called the zone "limits".  The lower limit is
 ;;  called the zone "beginning"; the upper limit is called its "end".
@@ -183,10 +195,10 @@
 ;;
 ;;  Basic-zone union and intersection operations (`zz-zone-union',
 ;;  `zz-zone-intersection') each act on a list of zones, returning
-;;  another such list, but which has POS1 <= POS2 in each of its
-;;  zones, and which lists its zones in ascending order of their cars.
-;;  For basic-zone union, the resulting zones are said to be
-;;  "coalesced", or "united".
+;;  another such list, but with the recorded positions for each zone
+;;  in (ascending) buffer order, and with the zones in ascending order
+;;  of their cars.  For basic-zone union, the resulting zones are said
+;;  to be "coalesced", or "united".
 ;;
 ;;  The extra info in the zones that result from zone union or
 ;;  intersection is just the set union or set intersection of the
@@ -201,24 +213,62 @@
 ;;  * The zones in the result list have been sorted in ascending order
 ;;by their first elements.
 ;;
-;;  * The zones in the result list are not adjacent and do not
-;;overlap: there is some other buffer text (i.e., not in any zone)
-;;between any two zones in the result.
+;;  * The zones in the result list are disjoint: they are not adjacent
+;;and do not overlap: there is some other buffer text (i.e., not
+;;in any zone) between any two zones in the result.
+;;
+;;
+;;(@* "Noncontiguous Region and Set of Zones")
+;;  ** Noncontiguous Region and Set of Zones **
+;;
+;;  Starting with Emacs 25, Emacs can sometimes use a region that is
+;;  made up of noncontiguous pieces of buffer content: a
+;;  "noncontiguous region".  This is similar to a set of zones, but
+;;  there are some differences.
+;;
+;;  The zones in a set (or list) of zones can be adjacent or overlap,
+;;  and their order in the set is typically not important.
+;;
+;;  A noncontiguous region corresponds instead to what results from
+;;  coalescing (uniting) a set of zones: a sequence of disjoint zones,
+;;  in buffer order, that is, ordered by their cars.
+;;
+;;  The Lisp representation of a zone also differs from that of a
+;;  segment of a noncontiguous region.  Each records two buffer
+;;  positions, but a zone can also include a list of additional
+;;  information (whatever you like).
+;;
+;;  A noncontiguous-region segment is a cons (BEGIN . END), with BEGIN
+;;  <= END.  A zone is a list (LIMIT1 LIMIT2 . EXTRA) of two positions
+;;  opti