diff options
author | Gerd Hoffmann <kraxel@redhat.com> | 2019-05-26 10:35:18 +0200 |
---|---|---|
committer | Gerd Hoffmann <kraxel@redhat.com> | 2019-05-26 10:35:18 +0200 |
commit | 49a5f59a2ee645c0e0f9271b3856c725997af248 (patch) | |
tree | b4423080c5fe9c1d321de388533f910e0e16a7bf | |
parent | 4963c96f323542134cae22435a579a9d039cb2cb (diff) | |
download | gterm-49a5f59a2ee645c0e0f9271b3856c725997af248.tar.gz |
text updates
-rw-r--r-- | README.md (renamed from README) | 9 | ||||
-rw-r--r-- | gterm.spec | 4 |
2 files changed, 8 insertions, 5 deletions
@@ -3,7 +3,8 @@ gterm ===== Terminal application, based on gtk3 and vte. The plan is to have a -modern terminal (which runs on wayland for example) for xterm fans. +modern terminal (which can -- for example -- run on wayland and render +emoji) for xterm fans. Command line options are compatible with xterm. Likewise config file key naming follows xterm resource naming. No config UI, you have to @@ -13,5 +14,7 @@ edit the ~/.config/gterm.conf config file, simliar to editing The number of supported config options is rather small right now, but is expected to grow over time to cover the most important ones. It will probably never fully match the xterm feature set though. Quite a -few xterm features are pretty much obsolete these days and will simply -not work with wayland, the x11 server side font rendering for example. +few xterm features are pretty much obsolete these days and/or will simply +not work with wayland. The x11 server side font rendering comes to mind +for example. Also any charset quirks dating back to the early x11 days, +before unicode and utf-8 did exist. @@ -11,8 +11,8 @@ BuildRequires: pkgconfig(gtk+-3.0) BuildRequires: pkgconfig(vte-2.91) %description -Terminal application, based on gtk3 and vte. The plan is to have a -modern terminal (which runs on wayland for example) for xterm fans. +Terminal application, based on gtk3 and vte. The plan +is to have a modern terminal for xterm fans. %prep %setup -q |