home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!sifon!thunder.mcrcim.mcgill.edu!mouse
- From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
- Newsgroups: comp.windows.x
- Subject: Re: Framemaker - X cut and paste
- Keywords: Framemaker, X, keyboard map
- Message-ID: <1992Dec23.163836.9583@thunder.mcrcim.mcgill.edu>
- Date: 23 Dec 92 16:38:36 GMT
- References: <1244@alsys1.aecom.yu.edu> <1h7r6cINNnp2@fnnews.fnal.gov>
- Organization: McGill Research Centre for Intelligent Machines
- Lines: 28
-
- In article <1h7r6cINNnp2@fnnews.fnal.gov>, shah@fnsony.fnal.gov (Hemant Shah) writes:
- > In article <1244@alsys1.aecom.yu.edu> you write:
- [I don't know who "you" is.]
- >> I have been trying to cut and paste between Framemaker and either
- >> xterm or xrolo (or any X-based application) without success. [The
- >> Framemaker] manual says that selected text is held in the X
- >> clipboard and may be pasted elsewhere. This is not true with the
- >> standard setup. [...]
- > The problem is with olvwm or olwm. They do not put the marked test
- > in X cut buffer.
-
- Which cut buffer? There are ten of them. And none of them are
- selections of any sort, including PRIMARY and CLIPBOARD.
-
- In any case, it's none of the window manager's business to meddle with
- selections and cut buffers.
-
- If Framemaker doesn't claim the PRIMARY selection when you select text
- in whatever the documented way is, it's buggy, and you should submit a
- bug report, and unless you have the source, hope the vendor feels like
- being nice to you. (Okay, perhaps that's a bit strong. It's possible
- that it was (mis)configured by whoever installed it to use whatever it
- is using rather than PRIMARY or CLIPBOARD or whatever.)
-
- der Mouse
-
- mouse@larry.mcrcim.mcgill.edu
-