summaryrefslogtreecommitdiff
path: root/st-0.8.4/LEGACY
diff options
context:
space:
mode:
authorstkhan <personal@slickd.xyz>2021-06-23 21:21:08 -0500
committerstkhan <personal@slickd.xyz>2021-06-23 21:21:08 -0500
commitd23e1969acfdb5d6212e3e796b33963d47e01c08 (patch)
treef0fa005a5c118ad00f23c4c68fe64d0712a2a285 /st-0.8.4/LEGACY
parent7ee7c74831b87a60291db335a272ed4ba3c27496 (diff)
sarc 1.0.0
Former-commit-id: 0154c723c80f3fec789ad09e43749cdffd0f6503
Diffstat (limited to 'st-0.8.4/LEGACY')
-rw-r--r--st-0.8.4/LEGACY17
1 files changed, 17 insertions, 0 deletions
diff --git a/st-0.8.4/LEGACY b/st-0.8.4/LEGACY
new file mode 100644
index 0000000..bf28b1e
--- /dev/null
+++ b/st-0.8.4/LEGACY
@@ -0,0 +1,17 @@
+A STATEMENT ON LEGACY SUPPORT
+
+In the terminal world there is much cruft that comes from old and unsup‐
+ported terminals that inherit incompatible modes and escape sequences
+which noone is able to know, except when he/she comes from that time and
+developed a graphical vt100 emulator at that time.
+
+One goal of st is to only support what is really needed. When you en‐
+counter a sequence which you really need, implement it. But while you
+are at it, do not add the other cruft you might encounter while sneek‐
+ing at other terminal emulators. History has bloated them and there is
+no real evidence that most of the sequences are used today.
+
+
+Christoph Lohmann <20h@r-36.net>
+2012-09-13T07:00:36.081271045+02:00
+