1qtermy(1)                   General Commands Manual                  qtermy(1)
2
3
4

NAME

6       qtermy - graphical TermySequence terminal multiplexer client
7
8

SYNOPSIS

10       qtermy [options]
11
12

DESCRIPTION

14       qtermy  is a graphical multiplexing terminal emulator client implement‐
15       ing the TermySequence protocol using the  termy-server(1)  multiplexing
16       terminal  emulator  server.   The emulator aims for XTerm compatibility
17       and supports modern terminal extensions such as 256-color  text,  mouse
18       tracking, shell integration, and inline image display. In addition, the
19       TermySequence protocol provides many features beyond standard  terminal
20       emulation,  including flexible, efficient connectivity between servers,
21       file monitoring and transfer, and multi-user terminal sharing and  col‐
22       laboration.
23
24       On  startup,  by  default  qtermy will attempt to connect to an already
25       running termy-server(1) instance using a per-user local socket. If  the
26       server  is  not  already  running,  it  will  be  launched. This server
27       instance is intended to be independent of user login  sessions  in  the
28       manner  of  tmux(1)  or screen(1) and is referred to as the "persistent
29       user server." Note that terminals launched on this  server  will  typi‐
30       cally  lack  the  environment variables needed to launch graphical pro‐
31       grams on the desktop, such as DISPLAY.
32
33       In addition, by default qtermy will launch  a  second,  private  termy-
34       server(1) instance as a direct child process. This server instance will
35       exit along with qtermy, but its terminals will have access  to  desktop
36       environment  variables  such  as  DISPLAY.   This  server  instance  is
37       referred to as the "transient session server."
38
39       Connections to additional termy-server(1) instances running in contain‐
40       ers,  on  other  hosts,  or as other users, including root, can be made
41       from qtermy or by using termy-connect(1) or its wrapper scripts  termy-
42       ssh(1), termy-su(1), and others.
43
44       qtermy listens on a per-user local socket of its own, which can be used
45       to launch remote pipe commands and application actions programmatically
46       using qtermy-pipe(1).
47
48       For comprehensive documentation of the many features offered by qtermy,
49       refer to the support pages at https://termysequence.io/doc/
50
51

OPTIONS

53       --noplugins
54              Disable loading all plugins.
55
56
57       --nosysplugins
58              Disable loading plugins from /usr/share/qtermy/plugins.
59
60
61       -t,--rundir dir
62              Look for the server's local socket under runtime directory  dir.
63              The  specifiers  %t and %U, if present, are expanded to the sys‐
64              temd runtime directory and the user UID respectively. Specifying
65              this  option  is  only  necessary if termy-server(1) is launched
66              with a custom runtime directory.
67
68
69       --tmp  Store the application's per-user local socket and other  runtime
70              files  under  /tmp  rather  than  $XDG_RUNTIME_DIR.  This is the
71              default unless systemd support is compiled in.
72
73
74       --nofdpurge
75              Don't look for and close leaked  file  descriptors  on  startup.
76              This is useful when debugging the application with tools such as
77              valgrind.
78
79
80       --version
81              Print version information
82
83
84       --man  Attempt to show this man page
85
86

FILES

88       $XDG_CONFIG_HOME/qtermy/
89
90       Location where qtermy stores its configuration files.
91
92       $XDG_DATA_HOME/qtermy/
93       /usr/share/qtermy/
94
95       Locations where qtermy looks for icons, images, plugins, and other data
96       files.
97
98       $XDG_CONFIG_HOME/qtermy/attr-script
99       /etc/qtermy/attr-script
100       /usr/lib/qtermy/attr-script
101
102       Programs  executed  by  qtermy  to  set client-specific UTF-8 key-value
103       pairs reported to servers and visible to  other  clients.  The  program
104       should  print  lines of the form key=value and must exit quickly. These
105       scripts are optional and are not required to be present.
106
107       A small number of basic client attributes, such as  the  UID,  are  set
108       directly by qtermy and cannot be changed from scripts.
109
110

NOTES

112       When  systemd(1)  is used to manage login sessions, certain administra‐
113       tive commands must be run to to allow the  persistent  user  server  to
114       survive  across  user login sessions.  Refer to termy-setup(1) for more
115       information.
116
117       qtermy has the ability to perform  remote  file  and  directory  mounts
118       using  fuse(8),  but  only if FUSE support was enabled at compile time,
119       the FUSE runtime is present on the system, and the user has the  neces‐
120       sary permissions to establish unprivileged FUSE mounts.
121
122

SEE ALSO

124       termy-server(1),  termy-connect(1),  termy-ssh(1),  termy-su(1), termy-
125       sudo(1), qtermy-pipe(1)
126       TermySequence - https://termysequence.io
127
128
129
130TermySequence™                    March 2018                         qtermy(1)
Impressum