From: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: [rudalics@gmx.at: Re: [simon.marshall@misys.com: mouse-autoselect-window needs a de lay]]
Date: Tue, 05 Sep 2006 17:59:01 +0200 [thread overview]
Message-ID: <44FD9EC5.2010000@gmx.at> (raw)
In-Reply-To: <85d5aalaoe.fsf@lola.goethe.zz>
>>A simple delay is standard for focus follows mouse policies. I don't
>>really want to omit that.
>
>
> It is not at all standard. For example, GNOME does not offer anything
> like that in its Window Preferences. What it _does_ offer is a dialog
>
> Window Selection
>
> [ ] Select windows when the mouse moves over them
>
> [ ] Raise selected windows after an interval
> Interval before raising: [0.0-10.0, default 0.5] seconds
>
> Deactivating any of those lines will deactivate the following lines.
> The default is "off" for all options.
I thought about KDE's "delay focus". Anyway `mouse-autoselect-window'
was and is by default nil. The question Kim raised was whether mouse
quiescence should be considered in the first place when delayed
autoselection is on. In this context I considered a simple timeout
"standard" because I know of implementations based on timeouts. I'm not
aware of attempts to check mouse quiescence with respect to focus
follows mouse.
> I actually know of no window manager offering a delay before select.
> If at all, they have delay before raise.
In general, window managers don't have the problem that selecting an
option from a menu-/toolbar should be interpreted in the context of a
particular window showing a particular buffer.
>>You can always set the delay to a very small value. In my
>>experience less than 0.2 seconds never sensibly delays selection but
>>may select the window too quickly. It depends on your mouse mileage
>>though, personally I like nervous mice.
>
>
> And unloaded machines and non-networked X11 connections. But not
> everybody is running Emacs on a machine of his dreams all of the time.
Correct. That's why this has to be more customizable.
next prev parent reply other threads:[~2006-09-05 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 15:17 [rudalics@gmx.at: Re: [simon.marshall@misys.com: mouse-autoselect-window needs a de lay]] Richard Stallman
2006-09-03 16:02 ` David Kastrup
2006-09-03 16:37 ` David Kastrup
2006-09-04 9:16 ` martin rudalics
2006-09-04 14:05 ` Kim F. Storm
2006-09-05 9:21 ` martin rudalics
2006-09-05 11:02 ` Kim F. Storm
2006-09-05 11:06 ` David Kastrup
2006-09-05 12:53 ` martin rudalics
2006-09-05 13:12 ` David Kastrup
2006-09-05 15:59 ` martin rudalics [this message]
2006-09-04 17:18 ` Richard Stallman
2006-09-03 17:05 ` Chong Yidong
2006-09-04 9:27 ` martin rudalics
2006-09-04 14:07 ` Kim F. Storm
2006-09-03 21:43 ` Kim F. Storm
2006-09-05 15:20 ` Stefan Monnier
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=44FD9EC5.2010000@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--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).