all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Boruch Baum <boruch_baum@gmx.com>, 27565@debbugs.gnu.org
Subject: bug#27565: 24.5; macro running feedback [enhancement request]
Date: Mon, 3 Jul 2017 13:56:31 -0700 (PDT)	[thread overview]
Message-ID: <83cd48b2-f7f8-49f0-a5bf-4b824d9b9b82@default> (raw)
In-Reply-To: <20170703183747.GF9438@E15-2016.optimum.net>

> Currently, when one invokes a macro, instead of an indication that
> the macro is running, the invocation key sequence is displayed

> I found the result disquieting:
> 
> 1] Did I forget to type something, and is emacs waiting for me to
> finish entering the command?
> 2] Did something crash?
> 3] Is anything happening?
> 4] Should I `C-g' and try again?

> ENHANCEMENT REQUEST: When a macro starts running, display a message
> in the mini-buffer. Some possible formats might be:
> a] macro [optional name] runnning . . .
> b] macro [optional name] runnning ( n of m times) . . .

+1.

Keep in mind, though, that keys used for the macro can
themselves invoke commands that also write to the echo area.

That's not a problem.  I'm just saying that between the
message "Keyboard macro running..." and the message
"Keyboard macro running...done" you might see other messages.

What if you expect the last key sequence invoked to show
you a message?  That would be overwritten by the "...done"
message, so you'd need to check buffer *Messages* for the
message you want.  Again, not a problem, I think.





  reply	other threads:[~2017-07-03 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 18:39 bug#27565: 24.5; macro running feedback [enhancement request] Boruch Baum
2017-07-03 20:56 ` Drew Adams [this message]
2021-02-05 12:23 ` Lars Ingebrigtsen
2021-03-12  1:55   ` Lars Ingebrigtsen

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=83cd48b2-f7f8-49f0-a5bf-4b824d9b9b82@default \
    --to=drew.adams@oracle.com \
    --cc=27565@debbugs.gnu.org \
    --cc=boruch_baum@gmx.com \
    /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.