Very nice, thanks. Looks fine on the pinephone in landscape mode, unfortunately it does not look as intended in portrait mode. That is using default st and font.
I noticed that on my desktop using zsh when calling it without parameters I get './wttr.sh: line 45: shift: shift count out of range'. I do not know whether that indicates a general problem.
I had some issues with getting the phone in a weird state where it was totally unusable using wakeup/sleep, did some experimentation and found a bunch more issues. I know how to work the buttons such that it works but it's not hard to trigger unintended behavior. I will try to document that cleanly somehow (including button timing, for which I'll need to come up with some syntax) soon™.
OK, that's an odd one. I didn't find any info on that but I believe you. Would be handy sometimes when editing commandlines on the phone. I guess I close this one then.
REPORTED RESOLVED NOT_OUR_BUG
What irritates me is that the huge conky clock will show the wrong time for a while after wakeup while the small clock in the status bar shows the correct time. I can easily imagine waking the phone to check the time and what you will look at is the large, wrong conky time. So a fix for this, and be it just a faster wakeup, would be really nice to have.
That function works just fine if you change the shebang to 'sh'. However, the output does not display nicely.
Something like 'curl "wttr.in/yourcity?format=4"' displays nicely but is only the current weather rather than a forecast. What is the command you used there for the portrait mode ~fjc?
Thanks for the explanation, I see now how the quoting works (but I'll need to read up more on that anyway).
Looks like that ModemManager patch is waiting for review by now, since a month. Is there anything we can do to move that forward?
This could have been the same issue: #306
I mean if I understand that correctly the quotation in this file at least is totally inconsistent. As an example, sometimes $TEXTID is quoted, sometimes, like in this line, it is not. Same for a bunch of other variables. I only stumbled upon that thanks to vis syntax highlighting. Some instances of the variables were white, others red because it matches pairs of quotation marks.
I do not think that you can nest double quotes, not even in shell scripting.
Whether that is the actual issue I do not know. I will try to find some time to fix the quotation and test it.
I do not fully understand what you mean, I use default ash.