t-8ch / taterm

tiling aware terminal

Taterm is a terminal emulator tailored to be used with tiling window managers. There may be special support for various window managers in the future.

Goals

• Keep the current directory over multiple invocations

  • Single instance via Gtk.Application

• Work on Wayland (maybe, didn't test)

• Use VTE3 (Don't need to reinvent the wheel and everything else around it)

• No gui clutter

  • Window, shell inside, period

• No tabbing (tiling window manager, remember?)

Features

• Single instance, directory is taken from last focused terminal
• Clicking of URIs
• Scroll lock (WIP)
• Clean build under latest GTK (3.3.18)

Prerequisites

• The Vala compiler
• libvte-2.91-dev

LICENSE

GPLv3

taterm's Issues

New windows are only notified, not raised

I'm not sure if it's the right place to report this, but if I launch a new taterm window while I'm focused on another window, it gets placed behind the focused window and I've got a notification that the app is ready.

I'm using Gnome Shell, and I know you're using a tiling WM so you certainly aren't annoyed by this issue, but it's a real pain for me since I've got to either alt-tab or click the notification bubble to raise the window.

I'm pretty sure it has to do with the fact that it's using GtkApplication and only spawning new windows, not apps, and the behaviour of not showing the window is intended (i.e. not configurable) in Gnome.

I do not know if there is a way to force new windows to bypass this restriction, so I'm asking it to you :)

Issue building taterm from aur

Hello, I noticed that you are also author of the package, the error on version 11-1 from https://aur.archlinux.org/packages/taterm/

==> Starting build()...
valac --pkg vte-2.91 --pkg gtk+-3.0 --fatal-warnings taterm.vala
taterm.vala:24.1-24.24: warning: the modifier `static' is not applicable to constants
static const string FONT = "11";
^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:25.1-25.28: warning: the modifier `static' is not applicable to constants
static const string[] COLORS = {
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:32.1-32.28: warning: the modifier `static' is not applicable to constants
static const string FG_COLOR = "#c0c0c0";
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:33.1-33.28: warning: the modifier `static' is not applicable to constants
static const string BG_COLOR = "#000000";
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:45.1-45.30: warning: the modifier `static' is not applicable to constants
static const string hex_encode = "%[0-9A-F]{2}";
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:46.1-46.32: warning: the modifier `static' is not applicable to constants
static const string common_chars = "\\\\a-z0-9-._~!$&'()*+,;=";
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
taterm.vala:47.1-47.32: warning: the modifier `static' is not applicable to constants
static const string regex_string =
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Compilation failed: 0 error(s), 7 warning(s)
make: *** [Makefile:7: taterm] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

Reading the color palette from Xresources would be nice

First off: thank you for this terminal. I really like it and I have already switched from rxvt-unicode.

There is one minor snag: The color palette is hard-coded. I like solarized and I have it set up in Xresources. It would be nice if this file was used to determine the color palette of taterm instead of having to hard-code it.

URL matching patterns do not match URL with # and ? and &

the following URL is not matched by the pattern

https://redmine.example.de/issues/121#somecomment

This renders such URLs unclickable which is inconvenient unfortuantely.