From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Insert at point (mouse copy/yank)
Date: Sat, 9 Oct 2004 11:14:04 -0700 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBEEEDCIAA.drew.adams@oracle.com> (raw)
In-Reply-To: <m3u0t3lr0z.fsf@newsguy.com>
mouse-yank-at-point non-nil should do what you want. Perhaps your Emacs has
a bug.
Try loading mouse.el (not mouse.elc), then M-x debug-on-entry
mouse-yank-at-click, then see what goes wrong (follow the code in mouse.el).
-----Original Message-----
From: Harry Putnam
I used to have something in .emacs that caused a yanked piece of text
from a mouse copy in other documents to be inserted at emacs point
rather than where ever the pointer happens to be.
Found this with M-x apropos <mouse.*yank><RET>
I'm not sure if this is related because it is set to t
mouse-yank-at-point's value is t
*If non-nil, mouse yank commands yank at point instead of at click.
You can customize this variable.
Defined in `mouse'.
next prev parent reply other threads:[~2004-10-09 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 17:50 Insert at point (mouse copy/yank) Harry Putnam
2004-10-09 18:14 ` Drew Adams [this message]
2004-10-09 19:55 ` Harry Putnam
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=FDELKNEBLPKKDCEBEJCBEEEDCIAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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.
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).