unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Live System User <nyc4bos@aol.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 33571@debbugs.gnu.org
Subject: bug#33571: 26.1.90; Artifacts in echo area
Date: Sun, 2 Dec 2018 15:18:54 -0800	[thread overview]
Message-ID: <09f05a2e-5b77-7a03-d38b-6ef5eeb171fb@cs.ucla.edu> (raw)
In-Reply-To: <87tvjv3awm.fsf@aol.com>

Live System User wrote:
>    I am seeing:
> 
>         C-g-
> 
>    remaining in the echo area (please note trailing hyphen "-") in
>    Emacs 27.

If I run 'emacs -Q' and type C-g, I see "Quit" in the echo area.

Perhaps you meant "C-c"? If I run 'emacs -Q' and type C-c and wait, I see "C-c-" 
in the echo area (with the trailing hyphen). However, that's normal and the 
behavior of Emacs hasn't changed there in quite some time. The trailing hyphen 
advises the user to type another keystroke in that context.

In the past, Emacs has had problems where the echo area wasn't cleared properly, 
and it sounds like you're seeing a bug in that area. However, I doubt whether 
any such bug is related to my recent changes to keyboard.c in the emacs-26 
branch. As Eli suggested, to debug your problem we'll need a complete 
stand-alone recipe for reproducing your problem, starting from 'emacs -Q'.





  reply	other threads:[~2018-12-02 23:18 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
2018-12-02 20:56         ` Live System User
2018-12-02 23:18           ` Paul Eggert [this message]
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=09f05a2e-5b77-7a03-d38b-6ef5eeb171fb@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=33571@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).