From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: nyc4bos@aol.com, 33571@debbugs.gnu.org
Subject: bug#33571: 26.1.90; Artifacts in echo area
Date: Sun, 02 Dec 2018 20:10:04 +0200 [thread overview]
Message-ID: <83woorajgj.fsf@gnu.org> (raw)
In-Reply-To: <07fec711-b1d3-fc22-83d7-61509ae41ac1@cs.ucla.edu> (message from Paul Eggert on Sun, 2 Dec 2018 09:43:26 -0800)
> Cc: nyc4bos@aol.com, 33571@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 2 Dec 2018 09:43:26 -0800
>
> Eli Zaretskii wrote:
> > Forget it, I reproduced this in texinfo-mode.
> >
> > This is indeed caused by the recent change in keyboard.c. Paul, could
> > you please take a look?
>
> What's the reproducer you used?
Visit a Texinfo file, then type "C-c C-c c".
> I tried visiting files in texinfo mode and
> couldn't see any difference in behavior. For example, if I start Emacs this way:
>
> src/emacs -Q doc/lispref/windows.texi
>
> and then type 'C-c /' quickly, it doesn't echo, and if I type slowly it does
> echo, and this is true for me in the emacs-26 branch regardless of whether the
> patch is installed.
Hmm... you are right. I guess I somehow unconsciously typed quickly
when testing without the patch and slowly with it.
I've reinstated the change on the emacs-26 branch. Sorry for the
noise.
I guess the bug should be closed as expected behavior, as I see that
all the way back to Emacs 22.1.
next prev parent reply other threads:[~2018-12-02 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 3:17 bug#33571: 26.1.90; Artifacts in echo area Live System User
2018-12-02 7:29 ` Eli Zaretskii
2018-12-02 7:43 ` Eli Zaretskii
2018-12-02 17:43 ` Paul Eggert
2018-12-02 18:10 ` Eli Zaretskii [this message]
2018-12-02 20:56 ` Live System User
2018-12-02 23:18 ` Paul Eggert
2018-12-03 1:16 ` Live System User
2018-12-03 5:57 ` Eli Zaretskii
2018-12-03 20:03 ` Live System User
2018-12-03 20:28 ` Eli Zaretskii
2018-12-03 21:06 ` Live System User
2018-12-04 6:34 ` 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=83woorajgj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33571@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=nyc4bos@aol.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 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).