Here are the frequently asked questions users typically ask about Tilix.
At this time there is no 32 bit version of Tilix available. Building and testing on 32 bit is a significant effort that we'd rather devote to development. The number of people using 32 bit Linux on the desktop is rather small and shrinking all the time so we feel it's the right choice at this time. Having said that, if people want to build and test Tilix on a 32 bit platform we'd be happy to accept any PRs to fix 32 bit issues.
At this point as of 17 July 2016, one PR that hopefully allows Tilix to compile and run as a 32 bit application has been accepted, however as per above no official project testing/support is being done to support this.
My background is in Java and J2EE and while I do some Python programming (via Jython), I have a preference for statically typed languages in the C family. I've played around with D in the past and have been impressed with it's language design and efficiency in comparison and coming from Java it was relatively easy to learn. Finally, D has a very complete GTK binding in the form of GtkD whereas other languages I considered (Go and Rust) do not.
Tilix complies with the Gnome HIG and the UI of Tilix is inspired by Gnome Builder. There is an option in Preferences to either shrink the terminal title bars or hide them completely.
Tilix supports session tabs since release 1.7.0. Under Preference -> Appearance, there is an option to use tabs instead of sidebar.
In Tilix the intention is that a split terminal should open in the same directory as the terminal that was split. The issue is caused by an issue in VTE configuration. This page has more information on the issue and how to correct it.
No, unfortunately using those require the use of a GTKScrolledWindow which is not supported by the VTE widget as per upstream.
Making scrollbars transparent requires CSS specific to that theme. At this time only Adawita, Ambiance, Radiance and the author's personal theme, Lavender, are supported.
That comes from powerline and is not something Tilix provides.
The following variables are supported:
| Variable | Description |
|---|---|
| ${title} | The title of the terminal |
| ${iconTitle} | The icon title of the terminal |
| ${id} | The numeric terminal ID (i.e. 1,2,3,4) |
| ${directory} | The current working directory in the terminal |
| ${columns} | The number of columns in the terminal |
| ${rows} | the number of rows in the terminal |
| ${hostname} | the hostname of the current session, availability dependent on the VTE script being configured on remote systems or triggers |
| ${username} | the current username, requires trigger support and an appropriate trigger be configured |
The following variables are supported:
| Variable | Description |
|---|---|
| ${appName} | The name of the application, i.e. Tilix |
| ${sessionName} | The name of the session |
| ${sessionNumber} | The number of the session, i.e. session 2 out of 4 active |
Background images requires transparency to work, in order to view the background image you need to adjust the transparency slider in the appropriate profile.
Tilix has a feature whereby it can send a notification to the desktop when a long running processes ends and Tilix is not visible. Additionally, if Tilix is the top level window but the process ended in a session which is not visible Tilix will display the notification in the header bar.
Currently notifications in Tilix required a version of the VTE widget that was patched by Fedora. This patch has not yet been accepted by upstream but is available in some other distributions such as Arch. In Arch it is available via the vte-notification-common and vte3-notification packages.
One reason this feature doesn't work on Arch is because of the VTE configuration issue. Please see this page for more information on it and how to correct it.
Currently building and running Tilix on Ubuntu 17.10 will lead to:
glib.GException.GException@../../.dub/packages/gtk-d-3.5.1/gtk-d/src/glib/GException.d(40): PCRE2 not supported
That happens because Ubuntu 17.10 hasn't updated VTE to PCRE2. Please see issue #916