@shekkiesqueaks AsciiDoc? If that's not it, check out https://en.wikipedia.org/wiki/List_of_markup_languages
Interesting 20 minute vid on soviet era computing there https://www.youtube.com/watch?v=TAFlVFT39Ik
xcalpr.c:89:21: error: initializer element is not constant
static FILE *fout = stdout;
Everything I'm reading says that hasn't been valid C since before ANSI standardization way back in the '80s.
Oh, duh. The Debian package page has a diff file downloaded separately, and some of them are patches to the C files fixing the compiler error I'm getting. Guess I should read it, edit the source, and re-diff them.
The latest date in xcal's CHANGES file is 1995-09-13.
@ticky Ruby's decisions about how to encode strings and when the default encodings are overridden mystify me. The String and Encoding class docs barely help me at all.
a mediocre coder who writes well is twice as valuable and ten times as teachable as a great coder who can't string words together
Programming which requires cussing:
If a native HDBF VM exists and GCC is ported to it, then it's all over.
Chromium on Wayland on Linux on Brainfuck.
Programming which requires cussing:
HDBF, Hyper-Dimensional Brainfuck: https://github.com/Property404/hdbf
... I'm afraid to write hello-world in it.
@Elizafox 2038: "Well, crap, Ada and COBOL had it right all along."
@nev 1. IDK. It feels like half the Web decided using CMSs reinventing the HTML wheel in JavaScript was only slightly less bad than reinventing it in Flash, thus A-OK and the way to go.
2. You're right, but without choosing to trust that their JS won't do funny things to my browser, I have no way of knowing whether or how much they detract from the story instead of help it.
"You fired you top talent. I hope you're happy.": https://medium.com/@deusexmachina667/you-fired-your-top-talent-i-hope-youre-happy-cf57c41183dd
Note: I disable JavaScript just about everywhere, and since Medium uses JS instead of HTML to embed images, that means I haven't seen any in the story.
As #OpenBSD's de-facto wifi maintainer, I first learned about this WPA problem in June. A simple patch was provided which I could commit with slight modifications.
The original embargo was already 2 months long, and then extended again for 2 months.
The generall public (you) were left in the dark about this for at least 4 months.
This is a very sad state of affairs. It takes the industry much too long to apply a simple patch.
Don't worry about today's WPA2 vuln if you're running #OpenBSD - both 6.1-stable and 6.2 release are already patched.
✨ Kind 'Net Help Desk fairy by day. ✨
✨ Weird & furry Unix fairy by night. ✨
✨ Sometimes a retrocomputer fairy. ✨
✨ Pays the ComputerFairi.es bills. ✨
✨ Sparkly✨shellscript✨princess. ✨
✨ Age: Mere days younger than ✨
✨ the Intel 4004 & Unix 1st Edition. ✨
✨ Follow requests welcome. ✨
✨
✨