« first day (3450 days earlier)      last day (1798 days later) » 

Tim
Tim
01:03
I was wondering if github.com/apache/spark has "issues"?
a feature by which I can ask questions
01:49
@Tim it seems as though they point to spark.apache.org/community.html which (ironically) points to Stack Overflow as well as some mailing lists.
 
5 hours later…
07:07
Does anyone understand what the plan on the far right means? hushed.com/pricing
Sorry about the off-topic, but I don't have a lot of people to ask.
On the top is says unlimited. Then further down it says 30 days.
The unlimited is the ∞s
07:24
@FaheemMitha It's the amount of data that is unlimited, not the timeframe.
08:05
@Kusalananda Oh, I see. Thank you.
@MichaelHomer Ok, so the time frame isn't unlimited. Thank you.
 
5 hours later…
13:31
Everyone seems to think that India is doing too little testing. I hope we're not on the verge of a mass outbreak.
 
4 hours later…
17:55
Hello, I have a question I'm not sure is worth asking on the main site
In the past I've had terminal glitches when using minicom or in rare cases SSH where the screen gets glitched with non-text characters. Then you need to run stty sane to fix it.
I need to get a screen shot of this glitch myself (due to copyright) but I can't seem to get it to occur. Does anyone know how I could go about triggering that manually?
This is the type of glitch I'm talking about cyberciti.biz/tips/bash-fix-the-display.html
18:24
You mean triggering the specific glitch you have or mimicking the output?
Would something like head /dev/urandom work?
I suppose there's all sorts of glitches possible besides just catting some binary
I think I could probably get away with /dev/urandom
@PhilipKirkbride What is this for? Just to explain to someone what it looks like? Can't you just use the image from the link?
29
Q: How to fix a terminal after a binary file has been dumped inside it?

alecailAfter having played with curl, a binary file has been dumped inside my terminal. For example, the horizontal lines: ─ I use to format my prompt are replaced by 'q', and it can be much worse. Why does this happen, and how can you fix it without having to close the terminal ?

18:39
@terdon it's for print
@JeffSchaller I saw that one but it doesn't seem to cause a continued glitch on Ubuntu 18.04, I could get an older virtual machine.
But after thinking about it I think just showing some output from /dev/urandom across with some explanation that you're basically stuck will be enough
stty -onlcr may help a bit, if you want to show continued input
@PhilipKirkbride ah
@JeffSchaller oh so normally stty sane will stop any ongoing output, but the stty -onclr is a sort of way around that?
running that stty will "garble" your next commands & output by stripping newlines (it seems)
oh awesome, yeah I just ran ls after and that is exactly the kind of thing I could use a picture of
18:45
excellent
 
2 hours later…
20:51
@terdon As you wish.

« first day (3450 days earlier)      last day (1798 days later) »