From: storm@cua.dk (Kim F. Storm)
Cc: jpw@shootybangbang.com (John Paul Wallington), emacs-devel@gnu.org
Subject: Re: suggested new command `picture-mouse-set-point'
Date: 25 Oct 2002 11:16:12 +0200 [thread overview]
Message-ID: <5x4rbazxnn.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200210242337.g9ONbr217063@rum.cs.yale.edu>
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
> > > One problem with this approach is that quite often you just need to
> > > click on some window to select another window or give focus to a frame
> > > -- and in that case you most likely don't want to modify the buffer if
> > > you accidentally click or a TAB or after EOL or EOB.
> > >
> > > Maybe the -rigidly functionality should only be activated if
> > > the mouse is clicked in the selected window & frame.
> >
> > I agree that is a problem, and your solution sounds good (or at least
> > the right sort of idea; I haven't tested it).
>
> I don't understand: this problem is not specific to this
> mouse-set-point-rigidly. Normally it is solved in a generic way
> by the window-manager by making sure that the click that changes
> focus is not sent to the application.
> Am I missing something ?
If I have just one frame with two windows, clicking the mouse in "the
other" window isn't a "focus change" event in the mind of the window
manager. So emacs must handle that case sensibly.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-10-25 9:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 18:04 suggested new command `picture-mouse-set-point' John Paul Wallington
2002-10-24 0:31 ` Kim F. Storm
2002-10-24 9:18 ` John Paul Wallington
2002-10-24 21:42 ` Kim F. Storm
2002-10-24 23:18 ` John Paul Wallington
2002-10-24 23:37 ` Stefan Monnier
2002-10-25 1:42 ` John Paul Wallington
2002-10-25 14:19 ` Stefan Monnier
2002-10-25 22:50 ` Kevin Ryde
2002-10-25 22:57 ` John Paul Wallington
2002-10-25 9:16 ` Kim F. Storm [this message]
2002-10-25 14:11 ` Stefan Monnier
2002-10-26 12:34 ` Kai Großjohann
2002-10-26 20:14 ` Richard Stallman
2002-10-28 15:20 ` Juanma Barranquero
2002-10-28 18:26 ` Eli Zaretskii
2002-10-29 7:23 ` Juanma Barranquero
2002-10-29 19:38 ` Eli Zaretskii
2002-10-29 3:01 ` Richard Stallman
2002-10-28 15:31 ` Juanma Barranquero
2002-10-29 3:02 ` Richard Stallman
2002-10-29 17:59 ` Juanma Barranquero
2002-10-30 11:55 ` Kim F. Storm
2002-10-30 12:47 ` Juanma Barranquero
2002-10-30 17:18 ` Richard Stallman
2002-10-30 17:51 ` Juanma Barranquero
2002-11-04 11:13 ` Juanma Barranquero
2002-11-04 15:02 ` Juanma Barranquero
2002-11-05 5:13 ` Richard Stallman
2002-10-26 20:13 ` Richard Stallman
2002-10-25 5:35 ` Richard Stallman
2002-10-25 9:49 ` Kim F. Storm
2002-10-26 20:15 ` Richard Stallman
2002-10-24 16:55 ` Richard Stallman
2002-10-24 23:21 ` John Paul Wallington
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=5x4rbazxnn.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=jpw@shootybangbang.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).