all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 7014@debbugs.gnu.org
Subject: bug#7014: 23.2; `C-h c' command doesn't show the info when invoked from the minibuffer
Date: Wed, 13 Jul 2011 08:30:28 +0200	[thread overview]
Message-ID: <CAH8Pv0jX8vo1NgR5njFPjK8e1i3ULEkguiSmkJ86FGZwAdsPNQ@mail.gmail.com> (raw)
In-Reply-To: <tx4o2rosnh.fsf@fencepost.gnu.org>

On Wed, Jul 13, 2011 at 03:50, Glenn Morris <rgm@gnu.org> wrote:
> Dani Moncayo wrote:
>
>> 2.- Type `C-x C-f'.
>> 3.- Now, from the minibuffer, type `C-h c' --> Here, Emacs prompts me
>> for a key to describe. OK.
>> 4.- Type `C-n' (for example). --> Now Emacs should show me the
>> description of the `C-n' key (*), but that doesn't happens. Instead,
>> after a couple of seconds, the minibuffer comes back with the prompt
>> of the `find-file' command.
>
> For me, the message "C-n runs the command next-line" appears for a
> second or two, then the "Find file" prompt reappears. This seems correct
> to me.
>

I've just checked this in [1], and I can confirm that:
1. It works right from plain "emacs -Q".
2. It is still reproducible if you disable blink-cursor-mode.


Footnotes
[1]
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2011-06-27 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt --cflags
-Ic:/build/include'


-- 
Dani Moncayo





  reply	other threads:[~2011-07-13  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11 19:22 bug#7014: 23.2; `C-h c' command doesn't show the info when invoked from the minibuffer Dani Moncayo
2011-07-13  1:50 ` Glenn Morris
2011-07-13  6:30   ` Dani Moncayo [this message]
2011-07-13  7:14     ` Eli Zaretskii
2012-09-07  5:01 ` Chong Yidong
2012-09-07 14:02   ` Drew Adams
2012-09-07 19:49     ` Dani Moncayo
2012-09-07 20:13       ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH8Pv0jX8vo1NgR5njFPjK8e1i3ULEkguiSmkJ86FGZwAdsPNQ@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=7014@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.