Everything you ever wanted to know about terminals
1–10 of 191 posts
Re: Everything you ever wanted to know about terminals
#2Off-topic, but it would be nice if HN could properly parse the Punycode encoding of internationalized domain names, so rather than the URL appearing as xn--rpa.cc, it appeared properly as ʞ.cc
Re: Everything you ever wanted to know about terminals
#3Jesus - now I’m afraid to know. But kudos what a wonderful resource.
It seems less and less people want to use the terminal.
All the new developers I notice want to stay in the IDE and almost never want to get their “hands dirty”.
Thanks for writing that great resource.
Re: Everything you ever wanted to know about terminals
#4Off-topic, but it would be nice if HN could properly parse the Punycode encoding of internationalized domain names, so rather than the URL appearing as xn--rpa.cc, it appeared properly as ʞ.cc
Showing the real url, followed by the Punycode url in brackets would be even better
Re: Everything you ever wanted to know about terminals
#5> but i swear to god developers have so completely forgotten how terminals work that i might be one of a handful of people left on earth who actually has the knowledge to, so they all just layer their bullshit on top of ncurses (which should never have survived the '90s) instead and it's ｍａｄｄｅｎｉｎｇ．
Actually, yes, understanding the tty in detail seems to become a dark art.
However it's the best way to do complex things quickly: I did use some of these tricks like storing and then restoring the cursor position to have the time at which a command stop executing ABOVE the command itself and next to the time it started executing in https://github.com/csdvrx/bash-timestamping-sqlite
I had to, because I was using MSYS2 and the time to execute a command was a limiting factor in Windows before WSL2.
Re: Everything you ever wanted to know about terminals
#6off topic but I would love a version of this with a more "plain" colors/ punctuation/formatting. finding it very hard to read / navigate
anyway the content looks good so will try to find time to sit down and read this "essay" soon
Re: Everything you ever wanted to know about terminals
#7I could take this a lot more seriously if capital letters were properly used.
Re: Everything you ever wanted to know about terminals
#8> but i swear to god developers have so completely forgotten how terminals work that i might be one of a handful of people left on earth who actually has the knowledge to, so they all just layer their bullshit on top of ncurses (which should never have survived the '90s) instead and it's ｍａｄｄｅｎｉｎｇ． Actually, yes, understanding the tty in detail seems to become a dark art. However it's the best way to do complex thing…
It looks like you have done a lot of work with sixels based on your github too. Have you ever written anything about that?
Re: Everything you ever wanted to know about terminals
#9off topic but I would love a version of this with a more "plain" colors/ punctuation/formatting. finding it very hard to read / navigate anyway the content looks good so will try to find time to sit down and read this "essay" soon
Some actual visual examples would've been nice, too. There is just text that describes what it would look like but, as we all know, one picture is worth a thousand words.
Re: Everything you ever wanted to know about terminals
#10off topic but I would love a version of this with a more "plain" colors/ punctuation/formatting. finding it very hard to read / navigate anyway the content looks good so will try to find time to sit down and read this "essay" soon
Some actual visual examples would've been nice, too. There is just text that describes what it would look like but, as we all know, one picture is worth a thousand words.
[deleted]