sagi/subsonic-tui
sagi/subsonic-tui
1
2
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
subsonic-tui/vendor/github.com/gdamore/tcell/v2/terminfo
History
Sagi Dayan 48661005be
initial commit 
Signed-off-by: Sagi Dayan <sagidayan@gmail.com>
2024-09-01 16:30:56 +03:00
..
a initial commit 2024-09-01 16:30:56 +03:00
b/beterm initial commit 2024-09-01 16:30:56 +03:00
base initial commit 2024-09-01 16:30:56 +03:00
c/cygwin initial commit 2024-09-01 16:30:56 +03:00
d/dtterm initial commit 2024-09-01 16:30:56 +03:00
dynamic initial commit 2024-09-01 16:30:56 +03:00
e/emacs initial commit 2024-09-01 16:30:56 +03:00
extended initial commit 2024-09-01 16:30:56 +03:00
f/foot initial commit 2024-09-01 16:30:56 +03:00
g/gnome initial commit 2024-09-01 16:30:56 +03:00
h/hpterm initial commit 2024-09-01 16:30:56 +03:00
k initial commit 2024-09-01 16:30:56 +03:00
l/linux initial commit 2024-09-01 16:30:56 +03:00
p/pcansi initial commit 2024-09-01 16:30:56 +03:00
r/rxvt initial commit 2024-09-01 16:30:56 +03:00
s initial commit 2024-09-01 16:30:56 +03:00
t/tmux initial commit 2024-09-01 16:30:56 +03:00
v initial commit 2024-09-01 16:30:56 +03:00
w initial commit 2024-09-01 16:30:56 +03:00
x initial commit 2024-09-01 16:30:56 +03:00
.gitignore initial commit 2024-09-01 16:30:56 +03:00
gen.sh initial commit 2024-09-01 16:30:56 +03:00
models.txt initial commit 2024-09-01 16:30:56 +03:00
README.md initial commit 2024-09-01 16:30:56 +03:00
TERMINALS.md initial commit 2024-09-01 16:30:56 +03:00
terminfo.go initial commit 2024-09-01 16:30:56 +03:00

README.md

This package represents the parent for all terminals.

In older versions of tcell we had (a couple of) different external file formats for the terminal database. Those are now removed. All terminal definitions are supplied by one of two methods:

  1. Compiled Go code

  2. For systems with terminfo and infocmp, dynamically generated at runtime.

The Go code can be generated using the mkinfo utility in this directory. The database entry should be generated into a package in a directory named as the first character of the package name. (This permits us to group them all without having a huge directory of little packages.)

It may be desirable to add new packages to the extended package, or -- rarely -- the base package.

Applications which want to have the large set of terminal descriptions built into the binary can simply import the extended package. Otherwise a smaller reasonable default set (the base package) will be included instead.