@MDXF Dಠne.

Thank yಠu!

given that Charcoal -v's been broken for some time, should I just push a potential fix to ASCII-only's GitHub (I had write access last time I looked) so that TIO can be unbroken?

@Neil That's something you should ask ASCII, not Dennis.

@Pavel sorry, somehow the bit about ASCII-only not being around to fix it for some time got lost while I was revising my question

Oh, yeah, you're right...

@Neil Maybe fix it on a different branch, and then make a pull request? Dennis could switch to that branch if he chose to.

@Neil If something's broken, I'd very much like to fix it. Whether you commit changes to master, a different branch, or a forked repo is between you and ASCII-only.

@Neil do we know where ASCII-only is? I haven't seen him in forever

The issue that affected TIO's data center was just marked as resolved. status.digitalocean.com/incidents/y7r95jywqhmy

@Dennis well that's not useful if I don't know where he is. I guess I could fork the repo, as that would be least surprising on his part.

My point is that it isn't up to me where I pull the changes from, but that I can pull them from anywhere. I don't know what you discussed with ASCII-only (if anything) when they gave you write access, but since they did, I'd assume they'd be comfortable if you fix something that's obviously broken.

I've forked it, it seemed safer. My fix is here: github.com/urkerab/Charcoal/commit/…

@Neil Pulled.

@Dennis Thanks!

Thank you! I was completely unaware that Charcoal was broken on TIO.

@Dennis Since when do the TIO input boxes grow when they get non-ASCII input?

@MDXF status-no-repro

The text areas grow automatically to accommodate whatever they hold. If you have a character that isn't supported by TIO's default font, it might be rendered too small or too large. The latter would resize the text area.

Really? No difference in the height of the code box between this and this?

@Dennis Ah that makes sense, it's just a bit annoying for characters that aren't actually too tall

And Kannada is definitely not part of DejaVu Sans Mono.

@MDXF There's nothing I can do about that. It's the size the font reports.

Welp now Cubically's comments are annoying :(

@MDXF You just said non-ASCII. Given those reproduction instructions, I tried ⍺⌈⌊_⎕'∩∘*○⍳∘↓, which didn't break it.

@Pavel I tried it with a few characters from Cubically's codepage and they all messed with it, sorry

Just a thought, getting the 60 seconds exceeded message on a cache hit is a bit odd, since the user doesn't see the 60 seconds passing.

The user still needs to know that the program was interrupted.

Maybe, "This request previously exceeded the 60 second time limit and was terminated; this result was cached."

@Dennis Could you pull Husk when you get the chance?

@Zgarb Done.

Thanks!

@Dennis Can you pull Add++ please?

@Dennis Ah, it's good to have the deverbosifier back, it help me golf another two bytes off codegolf.stackexchange.com/a/154175

Would't it make more sense to have -l print to STDERR?

@cairdcoinheringaahing Done.

@Dennis Thanks

@Dennis A friend of mine (who is learning programming in high-school, and has never heard of PPCG) just told me that he uses TIO to learn and play around with python.

I just thought you'd like to know that you've made an awesome tool with a bunch of people using it way beyond the scope you were originally intending it for. :)

:D

@Dennis It looks like Husk wasn't properly updated. This should return 6 but it errors for me

@H.PWiz That was a rather silly mistake on my part. Fixed.

Thanks