unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, 21313@debbugs.gnu.org
Subject: bug#21313: 25.0.50; Strange errors from dbus-handle-event
Date: Wed, 14 Oct 2015 21:37:17 +0200	[thread overview]
Message-ID: <876129gs2a.fsf@gnu.org> (raw)
In-Reply-To: <877foo4nkd.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> > There's also 30a6b1f81412044aa7dda5573b0142a0a03c4fd3, although it
>> > was supposed to deal only with recording input events for the
>> > purposes of keyboard macros.
>> 
>> I've been running with the latest master with that single commit
>> reverted for the past 10 days and never had this issue again.  So I'm
>> tempted to say that this commit is most probably the culprit.
>
> The only effect of that change is to call record_char on some events
> that might have evaded that before.  record_char does 2 things:
>
>  . it adds the event to recent-keys, a Lisp array
>  . it records the event as part of a keyboard macro, if a macro is
>    being recorded
>
> (There's also the "dribble" part, but I doubt that you are running
> with that enabled.)

No, I don't run that.

> So I wonder how could any of that cause the kind of trouble you
> reported.

Me, too.

> If you undo the revert of that commit, do you start seeing the problem
> again?

I'm back on master now so we'll see.

> If you do, please see which of the "unusual" events, if any, get
> passed to record_char, and whether they are recorded as part of
> recent-keys and keyboard macros

I added some debug code which spits out something like

record_char: 107
  -> NOT storing as part of macro
  -2> set to recent_keys at index 28

where the 107 is the result of formatting the Lisp_Object with "%S", the
second line indicates if store_kbd_macro_char is doing something, and
the -2> line means that the second ASET (recent_keys, ...) invocation in
record_char has been executed.

That's what you had in mind, right?

> (assuming that you are used to define and invoke macros in your
> routine work).

Yes, but not too frequently.  Macros haven't been involved when I had
those issues unless it is possible that some macro recording/replaying
I've done much earlier could have had a side-effect which appears much
later when killing text in a message-mode buffer.

Bye,
Tassilo





  reply	other threads:[~2015-10-14 19:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 16:24 bug#21313: 25.0.50; Strange errors from dbus-handle-event Tassilo Horn
2015-09-09 20:43 ` Tassilo Horn
2015-09-11 12:28   ` Tassilo Horn
2015-09-11 12:39     ` Eli Zaretskii
2015-09-11 13:06       ` Tassilo Horn
2015-09-11 13:59         ` Eli Zaretskii
2015-09-15 15:37           ` Tassilo Horn
2015-09-15 16:01             ` Eli Zaretskii
2015-09-16 11:39               ` Tassilo Horn
2015-09-22  5:49               ` Tassilo Horn
2015-09-22  8:00                 ` Robert Pluim
2015-09-22  8:21                   ` Tassilo Horn
2015-10-02 18:36                     ` Tassilo Horn
2015-10-02 19:05                       ` Eli Zaretskii
2015-10-02 20:33                         ` Tassilo Horn
2015-10-02 21:10                           ` Eli Zaretskii
2015-10-02 21:26                             ` Michael Albinus
2015-10-03  5:40                               ` Tassilo Horn
2015-10-03  6:32                                 ` Tassilo Horn
2015-10-03  7:14                                   ` Eli Zaretskii
2015-10-03  8:10                                     ` Tassilo Horn
2015-10-03  9:53                                       ` Eli Zaretskii
2015-10-03 12:06                                         ` Tassilo Horn
2015-10-03  7:43                                 ` Michael Albinus
2015-10-03  8:13                                   ` Tassilo Horn
2015-10-03  9:38                                     ` Tassilo Horn
2015-10-03 10:53                                       ` Eli Zaretskii
2015-10-14  9:58                                         ` Tassilo Horn
2015-10-14 17:05                                           ` Eli Zaretskii
2015-10-14 19:37                                             ` Tassilo Horn [this message]
2015-10-14 19:43                                               ` Eli Zaretskii
2015-10-15 11:37                                                 ` Tassilo Horn
2015-10-15 16:56                                                   ` Eli Zaretskii
2015-10-15 17:35                                                     ` Tassilo Horn
2015-10-15 19:44                                                       ` Eli Zaretskii
2015-10-16  4:53                                                         ` Tassilo Horn
2015-10-16  7:02                                                           ` Eli Zaretskii
2015-10-16  7:45                                                             ` Tassilo Horn
2015-10-16  8:23                                                               ` Eli Zaretskii
2015-10-16  9:25                                                                 ` Tassilo Horn
2015-10-16 10:11                                                                   ` Eli Zaretskii
2015-10-16 10:22                                                                     ` Tassilo Horn
2015-10-29  7:43                                                                       ` Tassilo Horn
2015-10-29 16:19                                                                         ` Eli Zaretskii

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=876129gs2a.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=21313@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.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).