From: John Paul Wallington <jpw@gnu.org>
Subject: Re: controlling echo during mouse-dragging
Date: Thu, 24 Jun 2004 23:58:05 +0100 [thread overview]
Message-ID: <87smckk1he.fsf@indigo.shootybangbang.com> (raw)
In-Reply-To: GWICc.10358$w3.4118@fe2.texas.rr.com
"David Vanderschel" <DJV4@Austin.RR.com> writes:
>> Please post some example code, preferably pared-down to essentials,
>> that demonstrates the problem.
>
> Actually, I am close to giving up now. I think I
> understand the problem. The fact is that any message
> in the echo area is erased on occurrence of the next
> input event. Normally mouse movement is not treated
> as an event, so one is not used to it causing erasure
> in the echo area. However, having invoked
> track-mouse, I am saying that mouse movement _is_ an
> event, so the echo area gets erased every time the
> cursor moves to a new character position. I do not
> see how to get around it.
Maybe you could display your message in the minibuffer rather than the
echo area? See `emerge-show-file-name' for example. It's hard to
tell whether that would make a difference without a concrete example
though.
next prev parent reply other threads:[~2004-06-24 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GRkCc.770$Pc.184@fe1.texas.rr.com>
2004-06-23 21:07 ` controlling echo during mouse-dragging John Paul Wallington
[not found] ` <sIoCc.966$Pc.886@fe1.texas.rr.com>
2004-06-24 15:46 ` John Paul Wallington
2004-06-24 22:52 ` David Vanderschel
2004-06-24 22:58 ` John Paul Wallington [this message]
2004-06-25 0:10 ` David Vanderschel
2004-06-25 0:11 ` David Vanderschel
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=87smckk1he.fsf@indigo.shootybangbang.com \
--to=jpw@gnu.org \
/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.
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).