unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Nick Roberts <nickrob@snap.net.nz>,
	emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: follow-link in grep buffer
Date: Fri, 25 Feb 2005 11:59:10 -0500	[thread overview]
Message-ID: <jwvu0o037m9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <x5ekf47fi9.fsf@lola.goethe.zz> (David Kastrup's message of "Fri, 25 Feb 2005 17:47:58 +0100")

>>> If we have specific problems in certain modes, let's fix those
>>> modes (e.g. in grep that you have to click on the file:line
>>> part of a line to jump).
>> 
>> AFAICT the specific problem at hand is that a mous-1 click used to
>> get focus should not follow a link.  No matter what kind of link, no
>> matter the major mode.

> That's not the only problem.  A mouse-1 click not used to get focus
> should follow a link.  If it doesn't, that is surprising.  Now
> click-to-focus is strictly a windowmanager and frame thingy.  While
> one also uses the mouse for the purpose of changing the _window_
> instead of the frame, one would be terribly surprised if this had not
> the side effect of setting point, too.  Basically, one sets point into
> a different window since that is the convenient way to change focus.

> It is completely backwards if this side effect of a window change
> leads to a link working or not working, namely if we _do_ set point,
> but _don't_ follow the link.  With a true click-to-focus, we should
> not even have the window-point change, merely the selected window.

AFAICT, the problem at hand is about frame-focus-changes, not about
window-focus-changes (Nick's message said "I might just want to select that
window to resize it" suggesting pretty clearly that he's talking about
frames rather than windows).

>> I think x-mouse-click-focus-ignore-position is pretty much the kind
>> of thing we want, although I'd have expected that the window-manager
>> would take care of those things (it should eat the "click-to-focus"
>> and not pass it on to the application).

> You are confusing frame and window.  Changing the selected window is
> also necessary at times.

No, I'm not confusing them, I was talking about frames (and never mentioned
the word "window"), tho I didn't make it explicit since I thought the
context was sufficiently clear.

BTW, in a click-to-focus environment (I'm still talking only about frames's
focus), I think it'd indeed also make sense (as Nick's message mentioned) to
ignore a click on a sensitive mode-line element if it was used to get focus.

Basically, any non-trivially-safe (point movement and window selection is
safe, most of the rest isn't) operation should not be triggered by
a click-to-focus.

Maybe the mouse-face should also be inactive on frames that don't
have focus.


        Stefan

  reply	other threads:[~2005-02-25 16:59 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 21:08 follow-link in grep buffer Nick Roberts
2005-02-21 21:19 ` Stefan Monnier
2005-02-21 22:48   ` Nick Roberts
2005-02-22  0:08     ` Drew Adams
2005-02-22  9:48       ` Kim F. Storm
2005-02-22 13:41         ` Stefan Monnier
2005-02-22 14:24           ` Kim F. Storm
2005-02-22 14:25           ` Kim F. Storm
2005-02-22 17:33         ` Drew Adams
2005-02-22  0:48     ` Jason Rumney
2005-02-21 21:45 ` Drew Adams
2005-02-21 22:20   ` Luc Teirlinck
2005-02-21 22:36     ` Nick Roberts
2005-02-21 22:46     ` David Kastrup
2005-02-21 23:00       ` Luc Teirlinck
2005-02-21 23:05       ` Luc Teirlinck
2005-02-21 23:42         ` David Kastrup
2005-02-22  0:00           ` Drew Adams
2005-02-21 23:07       ` Luc Teirlinck
2005-02-22  0:44       ` Jason Rumney
2005-02-22  1:26         ` David Kastrup
2005-02-21 23:06     ` Drew Adams
2005-02-21 21:45 ` Lennart Borgman
2005-02-21 21:46 ` David Kastrup
2005-02-21 22:46   ` Kim F. Storm
2005-02-21 23:22     ` Luc Teirlinck
2005-02-22 18:11 ` Richard Stallman
2005-02-25  6:51   ` Nick Roberts
2005-02-25  9:46     ` David Kastrup
2005-02-25 11:12       ` Kim F. Storm
2005-02-25 12:55         ` Stefan Monnier
2005-02-25 13:25           ` Lennart Borgman
2005-02-25 13:40             ` Kim F. Storm
2005-02-25 14:20             ` Andreas Schwab
2005-02-25 13:37           ` Kim F. Storm
2005-02-25 14:10             ` David Kastrup
2005-02-26 13:53               ` Reiner Steib
2005-02-27  0:32               ` Richard Stallman
2005-02-25 16:33             ` Stefan Monnier
2005-02-25 16:47               ` David Kastrup
2005-02-25 16:59                 ` Stefan Monnier [this message]
2005-02-25 23:05                 ` Lennart Borgman
2005-02-25 16:37             ` Drew Adams
2005-02-25 18:09               ` David Kastrup
2005-02-25 19:44                 ` Drew Adams
2005-02-25 20:07                   ` Stefan Monnier
2005-02-25 20:32                     ` David Kastrup
2005-02-25 20:53                     ` Drew Adams
2005-02-25 20:27                   ` David Kastrup
2005-02-25 21:24                     ` Robert J. Chassell
2005-02-25 23:34                     ` Drew Adams
2005-02-26  0:44                       ` David Kastrup
2005-02-26  1:18                         ` Drew Adams
2005-02-25 23:35         ` Kim F. Storm
2005-02-26  2:28           ` Stefan Monnier
2005-02-26  2:50             ` David Kastrup
2005-02-26  3:32               ` Stefan Monnier
2005-02-26 22:24             ` Kim F. Storm
2005-02-27  2:00               ` Stefan Monnier
2005-02-27  8:26                 ` Lennart Borgman
2005-02-27 21:46                   ` Stefan Monnier
2005-02-27 22:09                     ` Kim F. Storm
2005-02-28  1:03                     ` Nick Roberts
2005-02-25 22:53       ` Richard Stallman
2005-02-26  0:16         ` David Kastrup
2005-02-26 22:44           ` Kim F. Storm
2005-02-25 22:52     ` 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=jwvu0o037m9.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).