From 61ff6e97c57f62ee3ad4ffc2166e433bc060e7cb Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Tue, 16 Aug 2016 05:04:54 +0200 Subject: Integrated clipboard support * mapped to different registers beginning with "~" * on supported platforms accessing the clipboard is as easy as X~ or G~. Naturally this also allows clipboards to be pasted in string arguments/insertions (^EQ~). * Currently, Gtk+, PDCurses and ncurses/XTerm are supported. For XTerm clipboard support, users must set 0,256ED to enable it since we cannot check for XTerm window ops programmatically (at least without libX11). * When clipboard regs exist, the clipboard can also be deemed functional. This allows macros to fall back to xclip(1) if necessary. * EOL handling has been moved into a new file eol.c and eol.h. EOL translation no longer depends on GIOChannels but can be memory-backed as well. --- doc/sciteco.7.template | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) (limited to 'doc/sciteco.7.template') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index 9b31c7d..6ed89db 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -1267,6 +1267,53 @@ Their numeric parts are currently unused. The mechanisms involved are documented more elaborately in .BR sciteco (1). .TP +.BI ~ clipboard +These registers constitute \*(ST's support for system clipboards. +Clipboard support is highly UI-specific, so different +UIs might support different clipboards (or X11 selections) +or no clipboard at all. +\*(ST thus initializes registers beginning with \(lq~\(rq for +every available clipboard either on startup or only when +entering interactive mode. +The register \(lq~\(rq refers to the default clipboard which +will always exist if clipboards are supported. +Other commonly used clipboard registers are \(lq~P\(rq for the +primary selection, \(lq~S\(rq for the secondary selection and +\(lq~C\(rq for the clipboard selection. +The existence of a clipboard register can thus be checked +in macros to determine whether getting and modifying that +particular clipboard is supported natively. +.br +\*(ST does \fBnot\fP generally support clipboards on ncurses, +but has special support when used with a sufficiently recent version +of \fBxterm\fP(1). +Since the operability of XTerm clipboards cannot be tested +automatically, users will have to set the flag 256 of the +\fBED\fP flags if and only if their XTerm is configured for allowing +the \fISetSelection\fP and \fIGetSelection\fP window operations. +\*(ST will still check whether XTerm is actually used in +a particular session. +If native clipboard support is unavailable, users may +still fall back to using external tools like \fBxclip\fP(1) +with the \fBEC\fP command. +.br +Setting the string part of a clipboard register will set that +clipboard. \*(ST will perform automatic EOL-translation according +to the EOL-mode of the Q-Register view, so e.g. on Windows +clipboards will usually be set with the expected DOS linebreaks. +Appending to clipboard registers is currently not supported. +Furthermore, \*(ST will restore the contents of the clipboard +at the time of the operation when an assignment is rubbed out in +interactive mode. +When retrieving a clipboard register, the contents of the +clipboard at the time of the operation are returned. +EOL normalization will take place (if enabled), so that pasting +clipboards does not introduce unexpected EOL sequences. +The Q-Register view's EOL mode will \fBnot\fP be guessed from +the original clipboard contents, though. +The numeric parts of the clipboard registers are currently +not used by \*(ST. +.TP .BI ^F key Function key registers as documented in section \fBKEY TRANSLATION\fP. -- cgit v1.2.3