Timeline for What type of terminal to support if implementing a terminal emulator?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2019 at 19:52 | history | edited | JdeBP | CC BY-SA 4.0 | Fixed broken hyperlink. |
| May 14, 2018 at 6:42 | comment | added | telcoM | ...and before anyone else comments on this: yes, the termcap vs. terminfo is actually yet another difference between the legacies of BSD vs. SystemV. | |
| May 14, 2018 at 6:33 | comment | added | telcoM | Most command-line applications that need advanced TTY control won't implement it on their own, but use a library to handle the actual control codes. Historically, this library was known by the name curses; the modern version is ncurses. These libraries use a terminal description that identifies all the features available in a particular terminal type. The terminal description comes either from the terminfo database (modern) or from the /etc/termcap file (classic). So if you implement a new terminal type, you should also write a description for it and install it to your system(s). | |
| May 14, 2018 at 5:10 | history | edited | JdeBP | CC BY-SA 4.0 | Have some more further reading. |
| Jun 16, 2016 at 1:47 | comment | added | V.D.D | Especially, how can a custom terminal type like putty's work for the existing programs? | |
| Jun 15, 2016 at 10:55 | comment | added | V.D.D | So detailed! Before I decide whether to edit the question, I want to know how to make sure most commandline applications can run well in the terminal? | |
| Jun 15, 2016 at 9:36 | history | answered | JdeBP | CC BY-SA 3.0 |