lazygit/vendor/github.com/gdamore/tcell/v2/terminfo
2023-02-21 21:53:55 +09:00
..
a build: bump tcell version 2023-02-21 21:53:55 +09:00
b/beterm bump tcell 2021-06-06 09:12:42 +10:00
base use tcell via porting over code from awesome-gocui 2021-04-06 19:34:32 +10:00
c/cygwin bump tcell 2021-06-06 09:12:42 +10:00
d/dtterm bump tcell 2021-06-06 09:12:42 +10:00
dynamic bump gocui 2021-04-06 19:34:32 +10:00
e/emacs bump tcell 2021-06-06 09:12:42 +10:00
extended bump dependencies 2021-06-15 08:12:38 +10:00
f/foot build: bump gocui 2023-01-06 10:59:09 +09:00
g/gnome bump tcell 2021-06-06 09:12:42 +10:00
h/hpterm bump tcell 2021-06-06 09:12:42 +10:00
k bump tcell 2021-06-06 09:12:42 +10:00
l/linux bump tcell 2021-06-06 09:12:42 +10:00
p/pcansi bump tcell 2021-06-06 09:12:42 +10:00
r/rxvt bump tcell 2021-06-06 09:12:42 +10:00
s bump tcell 2021-06-06 09:12:42 +10:00
t bump gocui 2022-04-08 12:15:23 +10:00
v bump tcell 2021-06-06 09:12:42 +10:00
w bump tcell 2021-06-06 09:12:42 +10:00
x bump tcell 2021-06-06 09:12:42 +10:00
.gitignore use tcell via porting over code from awesome-gocui 2021-04-06 19:34:32 +10:00
gen.sh use tcell via porting over code from awesome-gocui 2021-04-06 19:34:32 +10:00
models.txt bump tcell 2021-06-06 09:12:42 +10:00
README.md use tcell via porting over code from awesome-gocui 2021-04-06 19:34:32 +10:00
TERMINALS.md use tcell via porting over code from awesome-gocui 2021-04-06 19:34:32 +10:00
terminfo.go build: bump gocui 2023-01-06 10:59:09 +09:00

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.