Difference between revisions of "Clipboard"

From ArchWiki
Jump to: navigation, search
m (Added link to list of clipboard managers on apps/utils wiki page)
(List of clipboard managers: added GPaste entrya)
(5 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
[[fr:Copier coller]]
 
[[fr:Copier coller]]
 
{{expansion}}
 
{{expansion}}
==History==
+
 
 +
== History ==
 +
 
 
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.
 
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.
  
==Background==
+
== Background ==
 +
 
 
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.
 
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.
 
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.
  
==Clipboard Managers==
+
== List of clipboard managers ==
There is a variety of clipboard managers available, and several desktop environments come with their own clipboard manager or have a clipboard manager intended for them ([http://glipper.sourceforge.net/ Glipper] for [[GNOME]] and [http://goodies.xfce.org/projects/panel-plugins/xfce4-clipman-plugin Clipman] for [[Xfce]]); however, there are several DE-agnostic clipboard managers such as [http://parcellite.sourceforge.net/ Parcellite] (GTK+) and [http://www.nongnu.org/autocutsel/ autocutsel] (command-line), both of which are available in [community] and can be run as daemons.
+
 
+
==Resources==
+
  
*[[List of Applications/Utilities#Clipboard_managers|List of clipboard manager packages]]
+
* {{App|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.|http://anamnesis.sourceforge.net/|{{AUR|anamnesis}}}}
 +
* {{App|ClipIt|Fork of Parcellite with additional features and bugfixes.|http://sourceforge.net/projects/gtkclipit/|{{Pkg|clipit}}}}
 +
* {{App|Clipman|A clipboard manager for Xfce. It keeps the clipboard contents around while it is usually lost when you close an application. It is able to handle text and images, and has a feature to execute actions on specific text selections by matching them against regular expressions.|http://goodies.xfce.org/projects/panel-plugins/xfce4-clipman-plugin|{{Pkg|xfce4-clipman-plugin}}}}
 +
* {{App|CopyQ|Clever clipboard manager with searchable and editable history, custom actions on items and command line support.|https://github.com/hluk/CopyQ|{{AUR|copyq}}}}
 +
* {{App|[[Wikipedia:Glipper|Glipper]]|Clipboard manager for the GNOME desktop with many features and plugin support.|https://launchpad.net/glipper|{{AUR|glipper}}}}
 +
* {{App|GPaste|Clipboard management system that aims at being a new generation Parcellite, with a modular structure split in a couple of libraries and a daemon for adaptability. Offers a GNOME Shell extension and a CLI interface.|https://github.com/Keruspe/GPaste|{{AUR|gpaste}}}}
 +
* {{App|[[Wikipedia:Klipper|Klipper]]|Full featured clipboard manager for the KDE desktop.|http://userbase.kde.org/Klipper|{{Pkg|kdebase-workspace}}}}
 +
* {{App|loliclip|Clipboard synchronizer developed for window manager users. Development ceased in favour of ''xcmenu''.|https://github.com/Cloudef/xcmenu|{{AUR|loliclip}}}}
 +
* {{App|Parcellite|Lightweight yet feature-rich clipboard manager.|http://parcellite.sourceforge.net/|{{Pkg|parcellite}}}}
 +
* {{App|Pasteall|Clipboard monitor simple and functional.|https://github.com/LaraCraft304/Pasteall|{{Aur|pasteall}}}}
 +
* {{App|xcmenu|Clipboard synchronizer developed for window manager users.|https://github.com/Cloudef/xcmenu|{{AUR|xcmenu-git}}}}
  
*[http://standards.freedesktop.org/clipboards-spec/clipboards-latest.txt Cut-and-paste in X]
+
== See also ==
  
*[http://www.jwz.org/doc/x-cut-and-paste.html X Selections, Cut Buffers, and Kill Rings.]
+
* [http://standards.freedesktop.org/clipboards-spec/clipboards-latest.txt Cut-and-paste in X]
 +
* [http://www.jwz.org/doc/x-cut-and-paste.html X Selections, Cut Buffers, and Kill Rings.]

Revision as of 13:17, 4 January 2014

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#)

History

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.

Background

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.
http://anamnesis.sourceforge.net/ || anamnesisAUR
  • ClipIt — Fork of Parcellite with additional features and bugfixes.
http://sourceforge.net/projects/gtkclipit/ || clipit
  • Clipman — A clipboard manager for Xfce. It keeps the clipboard contents around while it is usually lost when you close an application. It is able to handle text and images, and has a feature to execute actions on specific text selections by matching them against regular expressions.
http://goodies.xfce.org/projects/panel-plugins/xfce4-clipman-plugin || xfce4-clipman-plugin
  • CopyQ — Clever clipboard manager with searchable and editable history, custom actions on items and command line support.
https://github.com/hluk/CopyQ || copyqAUR
  • Glipper — Clipboard manager for the GNOME desktop with many features and plugin support.
https://launchpad.net/glipper || glipperAUR
  • GPaste — Clipboard management system that aims at being a new generation Parcellite, with a modular structure split in a couple of libraries and a daemon for adaptability. Offers a GNOME Shell extension and a CLI interface.
https://github.com/Keruspe/GPaste || gpasteAUR
  • Klipper — Full featured clipboard manager for the KDE desktop.
http://userbase.kde.org/Klipper || kdebase-workspace
  • loliclip — Clipboard synchronizer developed for window manager users. Development ceased in favour of xcmenu.
https://github.com/Cloudef/xcmenu || loliclipAUR
  • Parcellite — Lightweight yet feature-rich clipboard manager.
http://parcellite.sourceforge.net/ || parcellite
  • Pasteall — Clipboard monitor simple and functional.
https://github.com/LaraCraft304/Pasteall || pasteallAUR
  • xcmenu — Clipboard synchronizer developed for window manager users.
https://github.com/Cloudef/xcmenu || xcmenu-gitAUR

See also