From: Christoph Arenz <tiga.arenz@web.de>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Severe regressions in context of keyboard macros
Date: Sun, 29 Sep 2019 19:59:38 +0200 [thread overview]
Message-ID: <fdb6c4b1-6053-bfbb-0808-46507872b428@web.de> (raw)
In-Reply-To: <83mueoh6xn.fsf@gnu.org>
On 28.09.19 15:44, Eli Zaretskii wrote:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Sat, 28 Sep 2019 08:35:29 -0400
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>>
>> Anyway, my point is that maybe a better fix is to try and understand why
>> Calc does a read+unread and then figure out a way to get the same end
>> result without needing to read+unread.
That would definitely be the cleanest approach. As I understand it,
there are about 15 places in calc where it calls `calc-unread-command',
which then pushes events into unread-command-events and four more cases
in keypad.el without calling calc-unread-command.
Understanding the 'why' for every case probably requires someone with a
better expertise of calc than me...
> If someone is willing to do that, I'd of course encourage that.
next prev parent reply other threads:[~2019-09-29 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 8:17 Severe regressions in context of keyboard macros Christoph Arenz
2019-09-20 7:23 ` Eli Zaretskii
2019-09-20 15:43 ` Christoph Arenz
2019-09-20 17:54 ` Eli Zaretskii
2019-09-23 11:57 ` Christoph Arenz
2019-09-24 8:45 ` Eli Zaretskii
2019-09-26 10:46 ` Christoph Arenz
2019-09-26 10:56 ` Eli Zaretskii
2019-09-26 11:22 ` Christoph Arenz
2019-09-26 12:10 ` Eli Zaretskii
2019-09-26 18:27 ` Christoph Arenz
2019-09-28 9:18 ` Christoph Arenz
2019-09-28 9:46 ` Eli Zaretskii
2019-09-29 17:42 ` Christoph Arenz
2019-10-15 12:12 ` Eli Zaretskii
2019-09-28 12:35 ` Stefan Monnier
2019-09-28 13:44 ` Eli Zaretskii
2019-09-29 17:59 ` Christoph Arenz [this message]
2019-09-27 14:58 ` Fwd: " Christoph Arenz
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=fdb6c4b1-6053-bfbb-0808-46507872b428@web.de \
--to=tiga.arenz@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).