[jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[Richard Stallman]

Would someone please debug this, then ack?

------- Start of forwarded message -------
To: emacs-devel@gnu.org
From: JD Smith <jdsmith@as.arizona.edu>
Date: Wed, 06 Dec 2006 18:16:10 -0700
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Subject: mouse-yank-at-point in Comint modes
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4



COMINT modes like shell inhibit the behavior of mouse-yank-at-point.  

M-x shell
M-x set-variable [Ret] mouse-yank-at-point [Ret] t
% echo foo [C-a]
[Select text in another buffer and middle click into shell buffer, after
'foo']

Text is not yanked at point.  This is a new behavior of Emacs 22.

JD




_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------

Re: [jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[Romain Francoise]

Richard Stallman <rms@gnu.org> writes:

> Would someone please debug this, then ack?

I installed a fix for this.

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter

Re: [jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[Johan Bockgård]

Romain Francoise <romain@orebokech.com> writes:

> I installed a fix for this.

The call to `mouse-set-point' that was removed used to select the
comint window/buffer. After this change the code is executed in the
wrong buffer if a different window was selected before the click.

-- 
Johan Bockgård

Re: [jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[Romain Francoise]

bojohan+news@dd.chalmers.se (Johan Bockgård) writes:

> The call to `mouse-set-point' that was removed used to select the
> comint window/buffer. After this change the code is executed in the
> wrong buffer if a different window was selected before the click.

Ah, right.  It seems that trying to handle this case is hopeless because
when `mouse-yank-at-point' is t, yanking will always try to yank in the
wrong buffer if the target buffer is not current when Emacs receives the
event (since `mouse-yank-at-click' skips the `mouse-set-point' call in
that case).

So instead of adding a workaround for this problem, I just reverted my
change.  I guess that calling `posn-window' to select the window first
would work, but it's better left for later...

Thanks,

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter

Re: [jdsmith@as.arizona.edu: mouse-yank-at-point in Comint modes]

[Richard Stallman]

    Ah, right.  It seems that trying to handle this case is hopeless because
    when `mouse-yank-at-point' is t, yanking will always try to yank in the
    wrong buffer if the target buffer is not current when Emacs receives the
    event (since `mouse-yank-at-click' skips the `mouse-set-point' call in
    that case).

When `mouse-yank-at-point' is t, the right thing to do is look up the
binding in the selected window (if it is different from the one
clicked on) and run that binding.  Both `mouse-yank-at-click' and
`comint-insert-input' should do that.

That way, if a comint buffer is selected, and you click in another window,
`comint-insert-input' will do its thing.

We need to prevent this from recurring more than once.
So if the function looks up the binding and sees "it's me"
it should proceed to do its real job.