Years ago, I used Kate, no, not somebody’s wife, but the KDE Advanced Text Editor, to export source code files and fragments into HTML with syntax highlighting. I think that’s where I got the initial <b> idea from. There were also bucketloads of <span style='color:#644a9b;'> all over the place, even inside <b>. No CSS classes defined upfront, all colors inlined. The final rendering in the browser looked great, but the source code ugly as hell in my opinion. However, I’m thankful for hinting me at <b>. I think this kicked off everything. :-)
@movq@www.uninformativ.de It’s the “Lyse types the entire HTML by hand” generator. Yes, no kidding. I write articles so rarely, that I can do that once in a while. It’s fun to some degree, but also not.
After some time, I finally recorded some Vim macros to insert <b>…</b>, <var>…</var>, <span class=s>…</span> etc. around the tokens. This helped a little bit. But I was still questioning my mental state doing it like that. I also had to fix a bunch of the end tags by hand, because the word movement wasn’t enough or the end movement went too far. Quite the annoying process for sure.
But I think the HTML looks a wee bit nicer and is maybe even semantically a little bit better than having only <span>s everywhere. I find the <span class="whatever"> just soo awfully long. Of course, I never look at the code again, but knowing, that e.g. there is a <b> and it saves so many bytes in comparison, makes me happy. It is a more elegant solution in my opinion. Not by much, but better nonetheless. It’s a matter of simplicity. Admittedly, even I can’t avoid the <span>s alltogether. Oh well. On the other hand, I’m sure that this does not make any difference whatsoever. I bet, nobody and nothing, like a screenreader, analyzes the HTML for that, where this would be truly useful.
Oh! Maybe text browsers, though. It just occurred to me while composing this reply. :-) Haha, I lost my bet quickly. w3m picks up at least the <b> for keywords and builtin types, <u> for filenames and <i> for comments. Yey. No different styles for <var> and <mark>, unfortunately. elinks only renders the bold. It’s cool that I had the right intuition right from the beginning, despite being unable to pinpoint it. :-)
All the <span> hell with common syntax highlighters is a downer for me that keeps me from looking more into them. If I wrote more articles, I might rig something up with Pygments. At least that’s somehow positively connotated in my brain. Not sure if it actually deserves it, but I dealt with that in some loose form (can’t even remember) years and years ago. Apparently, it wasn’t too terrible.
To prepare the table of contents, I used grep and sed with some manual intervention in the end. The entire process can be improved. Absolutely.
You wrote your own site generator, didn’t you?
@movq@www.uninformativ.de Nice find!
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
@lyse@lyse.isobeef.org By the way, which site generator are you using? I kind of miss having code blocks with syntax highlighting and that generic yellow highlighting thing is pretty cool, too.
@lyse@lyse.isobeef.org lol, “garbo” 😅 Took me a moment. 🤣
@bender@twtxt.net Hahaha! :-D
I woke up well ahead of my alarm. But fear not, I’m tired, too. :-)
@garbo@www.uninformativ.de What a story! :-D
@kiwu@twtxt.net I like your enthusiasm. Go, go, go! :-)
@bender@twtxt.net Hahaha! :-D
Holy moly, these thunderstorm clouds are blacker than black, wow! The rain smells so wonderful. Yummy!
@bender@twtxt.net That certainly sounds much better in English, yeah. 😅
@movq@www.uninformativ.de hahahahaha! I’d say “Princess Grim Reaper” is more suiting. 😂
@bender@twtxt.net It started out as me calling myself “Princess Valium” because I’m so tired and braindead today, but then someone misheard that because a garbage truck drove by, and, so … one thing lead to another. 🤪 Sadly, it kind of fits, because I’m often the one who cleans up shit. 😬
@bender@twtxt.net LOL 😂
@movq@www.uninformativ.de but why? Are they that mean?! 😅
@kiwu@twtxt.net welcome, new slave! Err, I meant, beloved employee! 😅
@prologic@twtxt.net I do! I paginate usually 10 times on HN. Their algo is so messed up (but it works, I guess) that not doing that will make me miss a lot of good, interesting, things.
I join the tired masses. So tired, I slept through my alarm this morning (something that hasn’t happened for over 20 years, easily), and wife woke me up asking “Aren’t you going to work today?” So yeah, I could have slept for a while more this morning, for sure.
Same here, but my own fault
@kiwu@twtxt.net In-cred-ib-ly tired. 😂
Nobody ever does 🤣
Go get ‘em! 🙌
twtxt-lib (both v1 and v2, when the time is right), plus most of the other features (multiline, user-agent, and metadata), and I'm working on (re-)implementing threading, mentions, and hash filtering (to make conversations easier to follow).
Nice work! Threading + mentions is where it gets fun 😅 Ping me if anything in the spec is unclear 👌
Aha, my nickname at work now appears to be “Princess Garbage Disposal” (“Prinzessin Müllabfuhr”). 🤦♀️ 🥴
express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I've added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).
@prologic@twtxt.net @bender@twtxt.net Thanks! Yeah, it already supports Twt Hash via twtxt-lib (both v1 and v2, when the time is right), plus most of the other features (multiline, user-agent, and metadata), and I’m working on (re-)implementing threading, mentions, and hash filtering (to make conversations easier to follow).
Here’s a current snapshot of my local version, in case anyone is interested:
That reminds me, I need to update yarnd too. I haven’t done so yet 😅 Been so bloody busy with work 🥵