all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19718@debbugs.gnu.org, nandryshak@gmail.com
Subject: bug#19718: read_filtered_event echos mouse events until character is inputted
Date: Mon, 24 Jan 2022 18:19:12 +0100	[thread overview]
Message-ID: <87lez53vcf.fsf@gnus.org> (raw)
In-Reply-To: <87tuwrau0j.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Aug 2020 12:40:12 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> Because the echoing happens on a much lower level?
>
> So it's not on purpose, but just because that function uses lower-level
> functions that have this behaviour?
>
> Then perhaps those should be amended to allow inhibiting this echoing?

Yes, `read-event' does the outputting.  I've now fixed this in Emacs 29,
but I was unsure whether to add a new parameter, or extend the meaning
of the echo-keystrokes variable, so I did the latter -- nil (an
undocumented value) will now be even less updating than before.  I think
it kinda makes sense, but could see redoing this with an extra
parameter, too, if this leads to any issues.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-01-24 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 20:35 bug#19718: read_filtered_event echos mouse events until character is inputted Nick Andryshak
2018-05-15  2:43 ` Noam Postavsky
2020-08-25  9:54 ` Lars Ingebrigtsen
2020-08-25  9:58   ` Eli Zaretskii
2020-08-25 10:13     ` Lars Ingebrigtsen
2020-08-25 10:38       ` Eli Zaretskii
2020-08-25 10:40         ` Lars Ingebrigtsen
2022-01-24 17:19           ` Lars Ingebrigtsen [this message]
2022-01-27 15:21             ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lez53vcf.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19718@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=nandryshak@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.