From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: users and selection changes
Date: Fri, 15 Oct 2010 12:18:36 +0200 [thread overview]
Message-ID: <m3lj5zn4hv.fsf@quimbies.gnus.org> (raw)
In-Reply-To: buo62x3bxbw.fsf@dhlpc061.dev.necel.com
Miles Bader <miles@gnu.org> writes:
> If by "copying something in X" you mean, "select something in Xterm", then:
>
> (setq x-select-enable-primary t)
Yeah, I have that, but it... uhm. I could have sworn that didn't work!
But it does work now.
*scratches head*
I even wrote this thing because it didn't work:
(global-set-key [(hyper y)]
(lambda ()
(interactive)
(mouse-yank-primary (point))))
But I'm unable to not get it to work any more... Hm.
Sorry for the noise.
> The _problem_ with setting x-select-enable-primary is that now all
> _Emacs_ selections end up in the kill ring too, which is almost
> certainly Not What You Want.
Well, it doesn't really bother me. I don't use the mouse at all in
Emacs, so...
> My idea to get around that problem (expressed on the gnu.emacs.help
> newsgroup) is to add a feature that makes emacs put all selections
> _except_ those originating from itself (the current Emacs process) on
> the kill ring.
Sounds good to me.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-15 10:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 5:15 Custom themes Chong Yidong
2010-10-11 7:48 ` Deniz Dogan
2010-10-11 15:34 ` Chong Yidong
2010-10-11 16:09 ` Lars Magne Ingebrigtsen
2010-10-11 17:38 ` Chong Yidong
2010-10-11 21:04 ` Eric Lilja
2010-10-12 14:08 ` Joel James Adamson
2010-10-12 20:25 ` Chong Yidong
2010-10-12 23:40 ` Eric Lilja
2010-10-13 0:04 ` Christoph
2010-10-13 2:15 ` Chong Yidong
2010-10-13 20:06 ` David De La Harpe Golden
2010-10-14 4:23 ` Chong Yidong
2010-10-14 4:58 ` Miles Bader
2010-10-14 13:18 ` users and selection changes [was: Custom themes] Drew Adams
2010-10-14 18:35 ` Eli Zaretskii
2010-10-14 20:51 ` Drew Adams
2010-10-14 21:54 ` Eli Zaretskii
2010-10-14 22:09 ` Drew Adams
2010-10-15 9:30 ` Eli Zaretskii
2010-10-15 9:34 ` users and selection changes Lars Magne Ingebrigtsen
2010-10-15 9:45 ` Eli Zaretskii
2010-10-15 10:11 ` Lars Magne Ingebrigtsen
2010-10-15 10:16 ` Eli Zaretskii
2010-10-15 9:48 ` Miles Bader
2010-10-15 10:18 ` Lars Magne Ingebrigtsen [this message]
2010-10-15 13:47 ` Miles Bader
2010-10-15 14:25 ` Lars Magne Ingebrigtsen
2010-10-15 15:10 ` Eli Zaretskii
2010-10-22 10:05 ` Lars Magne Ingebrigtsen
2010-10-15 16:30 ` Drew Adams
2010-10-15 19:08 ` Stefan Monnier
2010-10-15 20:46 ` Chong Yidong
2010-10-13 0:26 ` Custom themes Stefan Monnier
2010-10-13 2:14 ` Chong Yidong
2010-10-13 10:20 ` Juanma Barranquero
2010-10-13 15:06 ` CHENG Gao
2010-10-13 16:05 ` Chong Yidong
2010-10-14 15:53 ` Chong Yidong
2010-10-14 16:47 ` Juanma Barranquero
2010-10-16 18:33 ` Chong Yidong
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=m3lj5zn4hv.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
/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).