bug#7014: 23.2; `C-h c' command doesn't show the info when invoked from the minibuffer

[Drew Adams]

> > I have not seen the fix yet, but I certainly hope that the 
> > currently active keymaps are used for this.
> 
> It's apparently so.
> 
> > In particular, with the example given, the doc for `C-n' 
> > should list the command it is bound to as being
> > `exit-minibuffer', since the question about its binding
> > is being asked with a minibuffer keymap current, and that 
> > is the binding of `C-n' in the minibuffer.
> 
> ?? `C-n' from the minifuffer doesn't exit the minibuffer.  It seems to
> be bound to `next-line', as reported if you do the experiment in the
> original message.

Sorry, I was thinking that the request example concerned `C-m' (`RET'), not
`C-n'.  (And of course for `C-m' the binding depends on which minibuffer map is
current.  It is `exit-minibuffer' in some cases but not all.)

> > This is important.  Emacs should always faithfully answer 
> > questions about itself and its current state.  When in the
> > minibuffer, users should be able to ask and get answers to
> > questions about the current, minibuffer, state.
> 
> Agreed, but that seems to be the current behavior.  Try for example
> [C-x C-f C-h c M-p].  Emacs will tell you that "M-p runs the command
> previous-history-element".  It looks ok to me.

Good.