From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: jpw@shootybangbang.com (John Paul Wallington) Newsgroups: gmane.emacs.devel Subject: Re: suggested new command `picture-mouse-set-point' Date: Fri, 25 Oct 2002 00:18:29 +0100 Sender: emacs-devel-admin@gnu.org Message-ID: References: <5xn0p4znhw.fsf@kfs2.cua.dk> <5xr8ef4ipi.fsf@kfs2.cua.dk> NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1035502427 20522 80.91.224.249 (24 Oct 2002 23:33:47 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 24 Oct 2002 23:33:47 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 184rU2-0005Ks-00 for ; Fri, 25 Oct 2002 01:33:46 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 184rWR-0002GF-00 for ; Fri, 25 Oct 2002 01:36:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 184r9T-0008SX-00; Thu, 24 Oct 2002 19:12:31 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 184r8r-0007Wp-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 19:11:53 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 184r8n-0007UC-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 19:11:53 -0400 Original-Received: from cmailm1.svr.pol.co.uk ([195.92.193.18]) by monty-python.gnu.org with esmtp (Exim 4.10) id 184r8n-0007R8-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 19:11:49 -0400 Original-Received: from modem-329.hodad.dialup.pol.co.uk ([62.25.161.73] helo=bundalo.shootybangbang.com) by cmailm1.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 184r8k-0003GY-00; Fri, 25 Oct 2002 00:11:47 +0100 Original-Received: from jpw by bundalo.shootybangbang.com with local (Exim 3.32 #1 (Debian)) id 184rFF-0007Cn-00; Fri, 25 Oct 2002 00:18:29 +0100 Original-To: storm@cua.dk In-reply-to: <5xr8ef4ipi.fsf@kfs2.cua.dk> (storm@cua.dk) X-Attribution: jpw X-Face: R(_z-rF:grdKO.*u`n);p.i $Eiz=h^CO5eDYv"4:K@#\HN09*Ykx}}B{kF/KH}%f_o^Wp > be funcalled where `mouse-set-point' is presently called directly, or > > `mouse-set-point' could call `mouse-set-point-rigidly' iff > > `mouse-set-point-rigidly' variable was non-nil, or something like > > that? > > It seems ok to control this behaviuor through a variable, but should it > be a customization option, or just intended for e.g. let bindings or > buffer-local (or mode-specific) setting? Maybe we need a user-option expressing a general preference and a programmatic variable that can be programmatically bound or set after it is made a local-variable? > 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). -- John Paul Wallington