unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Arenz <tiga.arenz@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: Severe regressions in context of keyboard macros
Date: Tue, 24 Sep 2019 11:45:35 +0300	[thread overview]
Message-ID: <83wodynkuo.fsf@gnu.org> (raw)
In-Reply-To: <a5802e94-3bbf-3e60-f844-0ff14cdec928@web.de> (message from Christoph Arenz on Mon, 23 Sep 2019 13:57:00 +0200)

> Cc: emacs-devel@gnu.org
> From: Christoph Arenz <tiga.arenz@web.de>
> Date: Mon, 23 Sep 2019 13:57:00 +0200
> 
> How about the following patch? It solved the calc bug for me and I could not find other regressions so far.
> Running make check showed no difference.
> As mentioned, I do not understand all potential effects, so it should be given some thoughts and tests.

Thanks, but I'd like to avoid changes in keyboard.c on behalf of input
recording issues, unless such changes are really a must.  In this
case, we already have 2 facilities to deal with unwanted repeated
recording of keys:

  . a Lisp program can bind inhibit--record-char to a non-nil value to
    avoid recording input events while some Lisp form is executed (you
    can see an example of using this in quail.el:quail-start-translation
  . a Lisp program can push onto unread-command-events a cons cell of
    the form '(no-record . KEY) to avoid recording KEY more than once
    (you can see an example of using this in
    cua-base.el:cua--prefix-override-replay)

Can you use one of these facilities to solve the issue in Calc?  Note
that you will need to build Emacs from the Git master branch to be
able to use these facilities, they are not available before Emacs 27.

Thanks.



  reply	other threads:[~2019-09-24  8:45 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 [this message]
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
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=83wodynkuo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tiga.arenz@web.de \
    /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).