Re: problems installing xquartz
Re: problems installing xquartz
- Subject: Re: problems installing xquartz
- From: Cameron Simpson <email@hidden>
- Date: Sat, 15 Dec 2012 08:46:11 +1100
[ Back on list - we're back in X11 land again... ]
On 14Dec2012 15:33, Jim Graham <email@hidden> wrote:
| On Sat, Dec 15, 2012 at 08:28:05AM +1100, Cameron Simpson wrote:
| > [ Off list, because this is just about email, not X11. ]
| >
| > On 14Dec2012 11:17, Jim Graham <email@hidden> wrote:
| > | > This email sent to email@hidden
| > |
| > | Nope. It was sent to the list.
| >
| > That message, I think, came from something intermediate, possible GMail,
| > to inform you of the target delivery address. It is not in the copy of the
| > email I got off the list.
|
| Oh, ok. I've never seen this before, so I assumed he'd added it.
|
| Strange. :-)
|
| Btw, the bit about autocutsel being (I'm guessing) bad turned out to be
| a great suggestion...it fixed my broken X11 --> OS X native copy/paste
| issue. :-)
I use autocutsel in native X11 setups, but xquartz' prefs settings do
essentially the same thing. PRIMARY isn't gone, but as Brandon says
there _are_ multiple cut/paste conventions in use _within_ different X11
apps. The two primary models are the xterm one where selection with the
mouse updates the app's paste buffer immediately and the "other" model
where selection just highlights text in that window and another action
is needed to put that text into the paste buffer, hence ^C on windows
and Command-C on Macs. In X11 this is complicated by have multiple paste
buffers, the early and simple PRIMARY and SECONDARY buffers, and the
slightly later CUT_BUFFERn (for n 0 through 9 I think) allowing a bunch
of active buffers. (And of course paste has its own choice about which
buffer to use).
Which style and internal implementation is used depends on both the app
_and_ the widget toolkit. Run multiple apps built against multiple
toolkits and you _will_ get lack of communication of cut buffer
contents. Historically xterm and Firefox always interacted badly this
way. Firefox is build on the Gnome toolkits, and this isn't something
you can switch away from without switching away from the app itself.
Autocutcel syncs the contents of the different schemes as they happen.
Discussing this is complicated by the fact that Gnome and KDE both
provide desktop environments / WMs, also generally just called "Gnome"
and "KDE".
I suspect you have switched away from the Gnome and KDE WMs to ctwm
(just as I use fvwm instead of Gnome or KDE). But the individual apps
you use will be using a widget toolkit, and that governs the mechanisms
of their cut/paste stuff.
Anyway, autocutsel is a good tool to bring consistent behaviour to this
realm of X11. And the modern xquartz releases (not the versions shipping
with the OX itself) seem to have pref options providing the same
facility, though they don't seem to do the job for you.
Cheers,
--
Cameron Simpson <email@hidden>
BSD code sucks. Of course, everything else sucks far more.
- Theo de Raadt (OpenBSD President)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden