bug#10416: 24.0.92; #'test-completion is inconsistent with symbol hash keys in COLLECTION

[Noam Postavsky <npostavs@users.sourceforge.net>]

[-- Attachment #1: Type: text/plain, Size: 170 bytes --]

tag 10416 + patch
quit

In 24.5 the 3rd case is fixed, but the docs are still contradictory as
of 25.0.94. Here is a patch to make manual agree with code and
docstrings.

[-- Attachment #2: 0001-Fix-documentation-of-completion-functions.patch --]
[-- Type: text/x-diff, Size: 1208 bytes --]

From dc25b98bf90b68b78c8b3baf4dcc0bbc609bd2d2 Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Tue, 7 Jun 2016 23:37:05 -0400
Subject: [PATCH] Fix documentation of completion functions

So that the behavior matches the match code (and docstrings).

* doc/lispref/minibuf.texi (Basic Completion): Symbol keys of hash table
are not ignored.
---
 doc/lispref/minibuf.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/lispref/minibuf.texi b/doc/lispref/minibuf.texi
index 6f41090..1fa2536 100644
--- a/doc/lispref/minibuf.texi
+++ b/doc/lispref/minibuf.texi
@@ -733,8 +733,8 @@ Basic Completion
 If @var{collection} is an obarray (@pxref{Creating Symbols}), the names
 of all symbols in the obarray form the set of permissible completions.
 
-If @var{collection} is a hash table, then the keys that are strings
-are the possible completions.  Other keys are ignored.
+If @var{collection} is a hash table, then the keys that are strings or
+symbols are the possible completions.  Other keys are ignored.
 
 You can also use a function as @var{collection}.  Then the function is
 solely responsible for performing completion; @code{try-completion}
-- 
2.8.0