From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: when to bind *down-mouse* vs *mouse*?
Date: Fri, 3 Dec 2004 09:22:25 -0800 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBKEAJCKAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200412030200.iB320CV26568@raven.dms.auburn.edu>
However, some of the standard bindings seem contradictory
- S-down-mouse-1 is bound to mouse-set-font.
- M-mouse-2 is bound to mouse-yank-secondary.
Can someone clear this up for me? What is the recommendation?
What is the logic behind mouse bindings for click events?
Are some of the standard bindings inconsistent, or am I just
missing something?
I do not see any inconsistency in the above. S-down-mouse-1 brings up
the Font menu and where you release it (S-mouse-1) determines what
happens next. I believe that it is in general preferable to bind
click events, rather than button-down events, unless you either want
to look for a drag type event or you want a two step process, like the
S-down-mouse-1 - S-mouse-1 sequence.
Thanks for your reply, Luc. I'm getting a better idea of what I'm missing.
I'm still unclear about S-down-mouse-1, however. What do you mean by "where
you release it (S-mouse-1) determines what happens next"? Maybe I'm missing
something because I'm using Emacs on Windows?
On Windows, S-down-mouse-1 just brings up the standard Windows Font dialog
box, by default. Where you release the mouse button does not seem to have
any effect.
I also tried setting `w32-use-w32-font-dialog' to nil, to get the
non-Windows dialog "like X does" (to quote the doc string). I still do not
notice any change in behavior depending on where I release the mouse button,
however.
What difference in behavior do you notice, depending on where you release
the mouse button?
Thanks,
Drew
next prev parent reply other threads:[~2004-12-03 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:28 when to bind *down-mouse* vs *mouse*? Drew Adams
2004-12-03 1:10 ` Andreas Schwab
2004-12-03 1:26 ` Drew Adams
2004-12-03 10:08 ` Andreas Schwab
2004-12-03 17:22 ` Drew Adams
2004-12-03 21:22 ` Andreas Schwab
2004-12-05 14:37 ` Richard Stallman
2004-12-03 2:00 ` Luc Teirlinck
2004-12-03 17:22 ` Drew Adams [this message]
2004-12-03 18:53 ` Luc Teirlinck
2004-12-04 10:19 ` Jason Rumney
2004-12-04 17:59 ` Alex Schroeder
2004-12-04 19:06 ` Lennart Borgman
2004-12-04 21:42 ` Jan D.
2004-12-05 0:10 ` Luc Teirlinck
2004-12-07 13:20 ` Jan D.
2004-12-06 19:16 ` Drew Adams
2004-12-06 20:10 ` Stefan Monnier
2004-12-08 1:38 ` Alex Schroeder
2004-12-08 19:06 ` Drew Adams
2004-12-08 19:45 ` Stefan Monnier
2004-12-08 20:42 ` Drew Adams
2004-12-09 4:42 ` Richard Stallman
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=FDELKNEBLPKKDCEBEJCBKEAJCKAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).