.TH gtk3-nocsd 1 "October 2015"
.SH NAME
gtk3-nocsd \- transparently disable Gtk+3 client side decorations (CSD)
.SH SYNOPSIS
.B gtk3-nocsd
\fIcommand\fR [ \fIcommand arguments\fR ... ]
.TP
.B symlinked-command
[ \fIcommand arguments\fR ... ]
.SH DESCRIPTION
\fBgtk3-nocsd\fR runs a command in the environment where Gtk+3 client side
decorations (CSD) are disabled, by using LD_PRELOAD to load the library
\fBlibgtk3-nocsd.so.0\fR that overrides some GLib, GDK and Gtk API calls
with customized variants.
.SH OPTIONS
.TP
.I command
The command to execute. It may be either a full path or the name of the command
in PATH. In case command cannot be found in PATH, \fBgtk3-nocsd\fR will fail.
.TP
.I command arguments
Arbitrary number of arguments to pass to the command being executed.
.SH INTEGRATION IN DEBIAN
.P
Usage of \fBgtk3-nocsd\fR is not required in Debian by default, because
gtk3-nocsd functionality is activated automatically on Xsession startup
if anything but GNOME is used. On GNOME CSDs will remain enabled. Both
the administrator and each individual user may override those defaults.
.P
Administrators may choose to re-enable CSDs by default by editing the file
.I /etc/X11/Xsession.d/01gtk3-nocsd
and changing the following setting:
.RS
.P
export GTK_CSD=1
.RE
.P
Users may choose to override this (in either way) by adding a similar line
to their
.IR ~/.xsessionrc .
For more details, please see
.IR /usr/share/doc/gtk3-nocsd/README.Debian .
.SH USAGE VIA SYMLINKS
If a symlink to \fBgtk3-nocsd\fR under a different name is called,
\fBgtk3-nocsd\fR will assume that the name it was called under is the name
of the command that is supposed to be executed. It will look for the command
in the PATH environment variable, excluding itself, and execute it with the
proper environment variables set. This is useful when is not desirable to add
gtk3-nocsd to the system-wide LD_PRELOAD or if it should be applied only to
certain applications.
.SH CAVEATS
.P
When using \fBgtk3-nocsd\fR with \fBsetarch\fR (including alias such as
\fBlinux32\fR), or anyway with chroots with different architectures than the
host's, make sure to install the matching architecture version of
\fBlibgtk3-nocsd.so.0\fR both in the \fBsetarch\fR environment and the host's
environment. Note that the \fBgtk3-nocsd\fR binary must then be installed in
a system path (\fI/usr/bin\fR, \fI/usr/local/bin\fR, ...), so that it will set
LD_PRELOAD to just the library name and let the dynamic linker find it
automatically - allowing the dynamic linker to pick the version for the
correct architecture. If \fBgtk3-nocsd\fR is not installed in a system path,
it will use a full path, allowing only for a single version of the library
to be used.