move consumer listing from channel to queue

The main motivation here is that queues, not channels, are the logical
home of subscriptions. And rabbit plug-ins and other extensions may
bypass channels when subscribing to queues.

The queues also know more about consumers than channels, namely
whether a consumer requires acks. So this additional info we can now
display too.

And with the switch to queues the listing is now scoped by vhost.

1 files changed, 13 insertions, 9 deletions

diff --git a/docs/rabbitmqctl.1.pod b/docs/rabbitmqctl.1.pod
index 3f1ec3b4e0..398ab613b6 100644
--- a/docs/rabbitmqctl.1.pod
+++ b/docs/rabbitmqctl.1.pod
@@ -430,15 +430,19 @@ QoS prefetch count limit in force, 0 if unlimited
 =item list_consumers
 
 List consumers, i.e. subscriptions to a queue's message stream. Each
-line printed shows, separated by tab characters, the id of the channel
-process via which the subscription was created and is managed, the
-consumer tag which uniquely identifies the subscription within a
-channel, and the name of the queue subscribed to.
-
-The list_queues, list_exchanges and list_bindings commands accept an
-optional virtual host parameter for which to display results,
-defaulting to I<"/">. The default can be overridden with the B<-p>
-flag.
+line printed shows, separated by tab characters, the name of the queue
+subscribed to, the id of the channel process via which the
+subscription was created and is managed, the consumer tag which
+uniquely identifies the subscription within a channel, and a boolean
+indicating whether acknowledgements are expected for messages
+delivered to this consumer.
+
+=back
+
+The list_queues, list_exchanges, list_bindings and list_consumers
+commands accept an optional virtual host parameter for which to
+display results, defaulting to I<"/">. The default can be overridden
+with the B<-p> flag.
 
 =head1 OUTPUT ESCAPING