From ArchWiki
Revision as of 11:35, 10 November 2013 by Flu (talk | contribs) (xcmenu added.)
Jump to navigation Jump to search

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Clipboard#)


In X10, "cut buffers" were introduced. These were limited buffers that stored arbitrary text and were used by most applications. However, they were inefficient and implementation of them varied, so selections were introduced. Cut buffers are long deprecated, and although some applications (such as xterm) may have legacy support for them, it is both not likely and not recommended that they be used.


The ICCCM (Inter-Client Communication Conventions Manual) standard defines three "selections": PRIMARY, SECONDARY, and CLIPBOARD. Despite the naming, all three are basically "clipboards". Rather than the old "cut buffers" system where arbitrary applications could modify data stored in the cut buffers, only one application may control or "own" a selection at one time. This prevents inconsistencies in the operation of the selections. However, in some cases, this can produce strange outcomes, such as a bidirectional shared clipboard with Windows (which uses a single-clipboard system) in a virtual machine.

Of the three selections, users should only be concerned with PRIMARY and CLIPBOARD. SECONDARY is only used inconsistently and was intended as an alternate to PRIMARY. Different applications may treat PRIMARY and CLIPBOARD differently; however, there is a degree of consensus that CLIPBOARD should be used for Windows-style clipboard operations, while PRIMARY should exist as a "quick" option, where text can be selected using the mouse or keyboard, then pasted using the middle mouse button (or some emulation of it). This can cause confusion and, in some cases, inconsistent or undesirable results from rogue applications.

List of clipboard managers

  • Anamnesis — Clipboard manager that stores all the clipboard history and offers an interface to do a full-text search. It has both a commandline and GUI mode available. || anamnesisAUR
  • ClipIt — Fork of Parcellite with additional features and bugfixes. || clipit
  • CopyQ — Clever clipboard manager with searchable and editable history, custom actions on items and command line support. || copyqAUR
  • Glipper — Clipboard manager for the GNOME desktop with many features and plugin support. || glipperAUR
  • Klipper — Full featured clipboard manager for the KDE desktop. || kdebase-workspace
  • loliclip — Clipboard synchronizer developed for window manager users. Development ceased in favour of xcmenu. || loliclipAUR
  • Parcellite — Lightweight yet feature-rich clipboard manager. || parcellite
  • Pasteall — Clipboard monitor simple and functional. || pasteallAUR
  • xcmenu — Clipboard synchronizer developed for window manager users. || xcmenu-gitAUR

See also