From: John Paul Wallington <jpw@gnu.org>
Subject: Re: controlling echo during mouse-dragging
Date: Thu, 24 Jun 2004 16:46:08 +0100 [thread overview]
Message-ID: <87acyt2c3j.fsf@indigo.shootybangbang.com> (raw)
In-Reply-To: sIoCc.966$Pc.886@fe1.texas.rr.com
"David Vanderschel" <DJV4@Austin.RR.com> writes:
>> > Is there any way I can prevent that uninformative "down-mouse-2-"
>> > echo from obliterating my infrequent attempts at informing the user?
>
>> Try binding `echo-keystrokes' to 0.
>
> OK, I tried that. I made echo-keystrokes buffer-local
> and set it to 0.
Hm. I meant `let' binding it when appropriate, but maybe that's
tricky -- are you tracking the mouse yourself or binding commands to
drag events, or something else ?
> This does prevent the "down-mouse-1-" 'keystroke' from appearing in
> the echo area.
Good :)
> However, my own messages are still being obliterated
> (with blankness) as soon as the cursor moves off of the character it
> was on when my program realized that it needed to offer new advice.
> Unfortunately, that is not satisfactory, as I do not want to have to
> repeat the message every time the mouse moves - just when it gets to
> certain special places (which is not too often).
>
> So I still have an obliteration problem; and now I do
> not even know what is causing it.
Please post some example code, preferably pared-down to essentials,
that demonstrates the problem.
next prev parent reply other threads:[~2004-06-24 15:46 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 [this message]
2004-06-24 22:52 ` David Vanderschel
2004-06-24 22:58 ` John Paul Wallington
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=87acyt2c3j.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).