Yep, that's true.
The case came with the Glove80, in fact it was shipped inside it.
Yep, that's true.
The case came with the Glove80, in fact it was shipped inside it.
Actually, it's not ronnabyte, it's ribibyte ...
Don't eat fast food, make your own.
Tiberius slaps Fisherman around a bit with a large trout.
Yep! Going to have a nice dinner paired with some nice kombucha and make it an early night. Happy new year and iwndwyt!
I'm not a materials scientist but you would think the edges of the cut holes are shedding particles in a larger degree than an intact pot. Wouldn't want that in something you're planning to ingest. My comment was made largely in jest, but I still think there's some truth to it, and we will look back on our plastic use with dread in the future.
Today's the day, it's been a year since I last had alcohol. God jul!
Are you trying to reach a URL on the same host you're ssh-ing to? That would create some interesting effects.
Especially since it works the second time it could mean that the second time you're actually on the host and ssh-ing to the host itself and then curling localhost.
Ah, I see. ~~I guess they get different contexts or something?~~ (Edit: I re-read your post and this does not make any sense :)) What if you chain the ssh command and the curl using &&?
Someone else suggested the env vars arent being expanded correctly inside the $(curl ...), which could be the culprit ... If a straight up URL works that would indicate that something like that is happening.
That said, I just tried setting an env var called URL="" and curling it, and curl said exit code 2, no URL specified, so something else is going on here.
True, true. I am very close to getting a Voyager for that use case, and for experimenting with different switches, etc, since its easier. I also think the QMK-based configuration the Glove uses is more powerful than the Voyager's system, but harder to use.