(webdev Tory) @worldsendless@qoto.org

I had a bash file that was suddenly failing. After TOO LONG debugging, I found that one of the included functions had been broken so it ended with `fi}` instead of `fi\n}` so a linebreak had been removed. As a result the cron job that depended on that script was failing. #BeautifulBash

ah, that's the stuff. Because Gnu `date` can create Julian dates but then cannot read them. #babashka #EayNumber #JulianDates #Clojure

@FinchHaven yeah, this instance has custom code and so deviated from the main branch, apparently a while ago

@borkdude thanks!

@javahippie @borkdude Thanks for that!

@borkdude you mean the `java.text.SimpleDateFormat` ? I searched all over the internet and that is the only thing I could find to get the function right

#Mastodon now has "edit post"? Since when?

@borkdude Well, it isn't one line, but it is basically one function. It took some research into how and what libraries to use, but here it is: https://gitlab.com/toryanderson/bb-julian-converter/

@borkdude sounds like it might turn out to be a one-liner then!

I can, for the moment, rest in peace (at least, on the issue of getting my portable docked triple-monitor setup stable with #exwm). https://orys.us/ww

Todo: write a #Clojure #Babashka script to convert from a given JDN to verbose date. So `babashka-date 2024030` => `Tue 2024.01.30`. Apparently GNU bash `date` can OUTPUT formats that it cannot intake.

@writh yeah, an old book from archive.org. Done right, epubs have certain advantages over pdfs. But apparently they can be done very wrong...

@freemo history? https://www.npr.org/2023/11/13/1211781246/unrwa-aid-gaza-palestinians-israel

#epub. A good thing: officially standardized by the W3C https://github.com/w3c/epubcheck . However, some auto-generated epub seems to be rubbish; 3 out of 4 of my epub readers failed to parse the epub, even after editing missing fields per https://www.edrlab.org/open-standards/anatomy-of-an-epub-3-file/ . I'm not sure how the 4th one managed it, but it's pretty ugly. Guess I'm sticking with #pdf on this one.

@Nundrum I found the issue, which was as stupid as I had suspected: I had something misspelled as "mastadon" rather than "mastodon", and it was looking for a function that didn't exist. Shadow should probably be more explicit about errors like that in my shadow-cljs.edn

My #ClojureScript #ShadowCLJS is not hotloading, although its codebase is just a copy of another that worked beatifully, and that a copy of another that never had troubles, either. I've looked over every difference I can find and see nothing. The WATCHER is working fine; when I make a code change, I see a spinner. But updates don't actually appear. React Devtools also show that nothing is connected. But manual hitting "refresh" works, though it feels like I'm back in the stone ages...