From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mac p9p snarf buffer
Date: Thu, 3 May 2007 20:00:50 -0400 [thread overview]
Message-ID: <20070504000050.GB62050@kris.home> (raw)
In-Reply-To: <20070503212009.AE2591E8C1F@holo.morphisms.net>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Thu, May 03, 2007 at 05:20:08PM -0400, Russ Cox wrote:
>+ X11 selections v. Pasteboard
>
>X11 doesn't have a snarf buffer. Instead it has an idea of which
>window currently "owns" the snarf (X11 would say `selection'), and
>when you want to find the snarf contents you go ask the current owner.
>There is no central buffer like on Plan 9's /dev/snarf or the Windows
>clipboard. (In addition to making things a lot more complicated, this
>means that snarf contents do not persist once their owner exits. But
>that particular problem isn't relevant here.)
As if that weren't bad enough, X11 *also* has central buffers, "cut
buffers", which are deprecated, but still used by some apps. And there
are 3 selections, PRIMARY, SECONDARY, and CLIPBOARD. Some apps,
expecially browsers and Gnome/KDEish apps, tend to use the PRIMARY and
CLIPBOARD selections, depending on what you're doing (middle click
pastes the PRIMARY, ^V pastes the CLIPBOARD). It's a terrific mess.
But let's not sully this list with X11 insanity any more.
--
Kris Maglione
If you lived here you'd be home now.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-05-04 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 21:20 Russ Cox
2007-05-04 0:00 ` Kris Maglione [this message]
2007-05-04 12:21 ` Derek Fawcus
2007-05-04 1:16 ` Scott Schwartz
2007-05-04 12:29 ` Derek Fawcus
2007-05-05 2:20 ` Kris Maglione
-- strict thread matches above, loose matches on Subject: below --
2007-05-03 16:37 Skip Tavakkolian
2007-05-03 16:45 ` Rob Pike
2007-05-03 17:45 ` David Leimbach
2007-05-03 17:52 ` Rob Pike
2007-05-03 18:09 ` Paul Lalonde
2007-05-03 22:55 ` Kris Maglione
2007-05-04 2:26 ` Russ Cox
2007-05-03 17:03 ` Anthony Sorace
2007-05-03 17:22 ` Russ Cox
2007-05-03 18:02 ` Skip Tavakkolian
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070504000050.GB62050@kris.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).