This is a grab-bag of topics that cover the bits you probably wouldn’t use in day-to-day activities.
Command line options¶
Various options can be passed to Terminator at startup time to change numerous aspects and behaviour.
The following option sub-sections can also be seen in the manual page for Terminator:
I’ve rearranged and grouped the options compared to how they
would appear using the
-h option just to aid clarity.
- Show a help message and exit
- Display program version
- Specify a config file
- If Terminator is already running, just open a new tab
- Use a different profile as the default
- Disable DBus
- Maximise the window
- Make the window fill the screen
- Disable window borders
- Hide the window at startup
- Set the preferred size and position of the window (see X man page)
- Specify a title for the window
- Set a custom icon for the window (by file or name)
- Specify a command to execute inside the terminal
- Use the rest of the command line as a command to execute inside the terminal, and its arguments
- Set the working directory
- Launch with the given layout
- Select a layout from a list
Custom Window Manager options¶
These settings are for people with heavy customisations to their window manager. Some window managers allow various rules to be applied, or actions to be taken, depending on how the window system perceives the window. These settings facilitate that.
- Set a custom WM_WINDOW_ROLE property on the window
In case you’re looking for the previously supported
classname setting, it has been removed as the gtk
libraries deprecated the function call that allowed forcing
the window class in this way.
See Debugging for more explanation of these options.
- Enable debugging information (twice for debug server)
- Comma separated list of classes to limit debugging to
- Comma separated list of methods to limit debugging to
The Config file¶
The default configuration file file for Terminator is stored in the standard path for configuration files. It can be found at:
It is human readable, and can be edited if you are are careful. This is not generally recommended though, and you are, of course, strongly advised to make a backup before making manual changes.
There are many more specific details in the manual page:
If you place items in the wrong location within the config file it can cause unintended results. In the worst case Terminator will fail to load. In the best case it will have no effect and you will simply confused as to why your change has made no difference.
There is inbuilt debugging features in Terminator. The simplest is to
start Terminator from another terminal application (i.e. gnome-terminal)
with the option
-d. This will dump many debug statements to the
If the DBus is active in any other Terminator, then by
default your attempt to launch with debug will launch
a new window under the already running process. To prevent
this you can use the
-u option which will disable the
DBus interaction for the debugged instance of Terminator.
There is a lot of output, and a great deal of it will typically not be related to the area you are looking into. There are two more options that can be passed that limit the amount of debug lines to classes or methods of interest. See Debugging options for the detail.
The final facility is to start a debug server by passing
is the same as
-d -d) which will start a debug server. With this
setting a fourth item, Open Debug Tab, also appears in the second
part of the The Context Menu, as highlighted in the image to the
Selecting it will give the following new tab with dedicated debug terminal:
This prompt is a standard Python interactive prompt, but this is connected to the Terminator instance. You can explore the applications data structures, classes, etc. and can even call functions and methods.
Alternatively, instead of launching this tab, you could connect to the debug server from a different window. This requires that you search back through the debug output for the line containing “listening on”. Here you will see the port number, and you can simply use:
$ telnet localhost <port>
Whichever method you use the debug output is also dumped into this terminal, even though it is already there in the launching terminal. This can get rather annoying, and seems counter-productive to me, so a way to turn off the output in the debug console may be added. In the meantime you can use:
>>> from terminatorlib import util ... util.DEBUG=False
This should turn off the output, and let you explore the internal structure more easily.
-dd option will make the DBus
interface temperamental. Any attempt to use Remotinator
will hang the main application.
The debug options and their usage are detailed here.
DBus is a standardized form of IPC, or Inter-Process Communication. More detail about the internals of DBus can be found at the freedesktop.org for DBus.
In Terminator we currently use DBus for two tasks:
Only run one instance of Terminator
The first instance will create the server. The second instance will fail to create the server, so it will request the first instance to create a new window (or new tab with
Running a single instance of Terminator can cause behaviour
that is unexpected by the user when a terminator instance
is already running. They do not have seperate processes,
and currently some features (in particular broadcast, and
grouping keys) may include more terminals than you expect.
You can work around this by using the
-u option that
will disable the DBus for that secondary instance.
The Layout Launcher already does this for you, and as a
result any layout launched this way is running without
DBus, and cannot be controlled with DBus. If you use the
command line option
-l <LAYOUT_NAME> to open a new
layout, this will not disable the DBus unless you
explicitly add the
-u option too.
There is quite some scope for improving this. I have a vague notion of a single master server and multiple instance servers, to improve the interaction between DBus and layouts.
Remotinator is a minimal wrapper around making DBus calls, and is
typically run from within a Terminator terminal. This is not
strictly necessary but, if you do not, you will have to do some extra
work to determine the valid UUID of a current terminal and pass it as
TERMINATOR_UUID environment variable, or as the value to the
--uuid option. Remotinator is called within Terminator
$ remotinator <command>
or with one of the following:
$ remotinator --uuid <UUID> <command> $ TERMINATOR_UUID=<UUID> remotinator <command> $ export TERMINATOR_UUID=<UUID>; remotinator <command>
to force the UUID, or call it from outside Terminator.
There are a couple of commands that do not require a UUID. Please see the table below for details.
The following commands are currently enabled:
|get_tab||Get the UUID of a parent tab|
|get_tab_title||Get the title of a parent tab|
|get_terminals ||Get a list of all terminals|
|get_window||Get the UUID of a parent window|
|get_window_title||Get the title of a parent window|
|hsplit||Split the current terminal horizontally|
|new_tab||Open a new tab|
|new_window ||Open a new window|
|vsplit||Split the current terminal vertically|
|||(1, 2) These commands do not require the UUID. If not marked as such then the command does require the UUID.|
Calling Remotinator without a command or with the
-h will print
the options and available commands to the terminal.
If a layout has been launched using the The Layout Launcher
or using the
-u option Remotinator will not work
with that layout as it is not connected to the DBus session.
As mentioned in the DBus section, this has the potential to be improved upon.
There is a lot of scope for expanding the available commands, and it is relatively simple to do, so is an ideal task for dipping ones toes.