public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: Clipboard periodically breaks
Date: Thu, 21 Nov 2013 17:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> On Thu Sep 26 20:35:21 2013, Matt D. wrote:
>> However, an environment variable that tells it which clipboard to
>> use would provide an immediate solution and be used used on a
>> per-application basis. For example, I can use aliases when launching
>> programs:
>> $ xclip=clipboard1 gedit $@ (monitor only clipboard 1)
>> $ xclip=clipboard2 gedit $@ (monitor only clipboard 2)
>> No option would indicate that both clipboard 1 and clipboard 2 would
>> be handled as they are now.
>> I'm not familiar with X programming but I'm assuming here that it
>> would be possible for xclip to read from a particular process's own
>> environment (rather than xclip's own) while processing a clipboard
>> event to do this.
>> What do you think?

This is not straightforward to implement and is not really a good solution as
it won't work for remote X clients.

In theory, it might be possible to annotate the X client window with a
property which tells XWin/xwinclip how to treat it's clipboard use, but since
the clipboard-owning window is often a hidden one, getting that property on
there poses problems.

Hopefully the -noprimary option makes this less of an issue.

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

      parent reply	other threads:[~2013-11-21 17:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 18:59 64-bit Clipboard troubles David Stacey
2013-06-10 13:30 ` Jon TURNEY
2013-06-10 21:39   ` David Stacey
2013-06-21 12:33     ` Jon TURNEY
2013-06-21 18:02       ` David Stacey
2013-09-22  2:39       ` Clipboard periodically breaks Matt D.
2013-09-22  3:11         ` Matt D.
     [not found]         ` <>
2013-09-27  0:35           ` Matt D.
2013-10-21 14:46             ` Reinier Post
2013-10-21 22:37               ` Matt D.
2013-11-21 17:51               ` Jon TURNEY [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).