Hacker Newsnew | past | comments | ask | show | jobs | submit | NotTheDr01ds's favoriteslogin

Human:

Did you know that there is no country in Africa that starts with the letter "k"?

ChatGPT:

Yes, that's correct! While there are 54 recognized countries in Africa, none of them begin with the letter "K". The closest is Kenya, which starts with a "K" sound, but is actually spelled with a "K" sound. It's always interesting to learn new trivia facts like this.

www.emergentmind.com/posts/did-you-know-that-there-is-no-country-in-africa-that


Skip the speech-to-text step, grab the subtitles from youtube.

I'm pretty sure it's a version + terminal + configuration issue.

I work in terminals all day long at home and work. I have a consistent user profile. On the other hand different operating systems have different terminals. I've seen the symptom occur locally (Ubuntu -> Gnome-Terminal -> bash -> tmux) and usually go away after an update of one of the components. But most frequently it occurs when crossing boundaries ({Windows, Fedora, Ubuntu} | {putty,gnome-terminal,tilix,serial tty} | tmux | literally anything). It happens more frequently when embedding tmux sessions while crossing those boundaries.

I _really_ wish there existed some software which would try to debug terminal display issues, even if it involved echoing something in a client program and then asking me "does this show up as intended and/or garbled?", with a timeout value for "it's so garbled that the user couldn't read or respond" similar to configuring a video display.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: