unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Chong Yidong <cyd@gnu.org>
Cc: 10224@debbugs.gnu.org
Subject: bug#10224: 24.0.92; M-w inhibits echoing of prefix arguments
Date: Tue, 06 Dec 2011 08:30:54 +0100	[thread overview]
Message-ID: <87zkf6dump.fsf@escher.fritz.box> (raw)
In-Reply-To: <87wraav51r.fsf@gnu.org> (Chong Yidong's message of "Tue, 06 Dec 2011 09:53:52 +0800")

On Tue, 06 Dec 2011 09:53:52 +0800 Chong Yidong <cyd@gnu.org> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> 1. emacs -Q
>> 2. Type `C-u' => in the echo area you see "C-u-"
>> 3. Set the mark (e.g. by typing `C-SPC') and then type `M-w'.
>
> I don't understand what you are trying to say.
>
> After typing C-u, if I immediately type C-SPC, Emacs says "No mark set
> in this buffer".  That is to be expected, since C-u C-SPC is supposed to
> move point to the mark.
>
> Could you repeat with the *exact* recipe?

Sorry for the confusion.  Step 2 was only meant to demonstrate the usual
echoing of prefix arguments; it's not a necessary step to get the bug.
Step 3 is really the entire recipe: after setting the mark (in any way)
and then typing M-w, all subsequent interactively typed prefix arguments
are no longer echoed.  (Under conditions I haven't yet been able to
determine, the echoing sometimes returns after a while, but immediately
vanishes again upon typing M-w (if the mark is set).)

Steve Berman





  reply	other threads:[~2011-12-06  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 20:27 bug#10224: 24.0.92; M-w inhibits echoing of prefix arguments Stephen Berman
2011-12-06  1:53 ` Chong Yidong
2011-12-06  7:30   ` Stephen Berman [this message]
2011-12-06  8:17     ` Chong Yidong
2011-12-06  9:00       ` Stephen Berman
2011-12-09  5:52         ` Chong Yidong
2011-12-11 17:52           ` Stephen Berman
2012-02-26 10:00             ` Chong Yidong
2012-02-26 21:27               ` Stephen Berman
2020-08-25 12:58 ` Lars Ingebrigtsen
2020-08-25 18:02   ` Stephen Berman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87zkf6dump.fsf@escher.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=10224@debbugs.gnu.org \
    --cc=cyd@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).