(#i6mgd3a) @movq@www.uninformativ.de What worked? š
#dhyiypa
(#i6mgd3a) @movq@www.uninformativ.de What worked? š
My mate and I went on a hike earlier. Yesterday, we had lovely 12°C. But today, it was down to at most 4°C. Oh well. At least the sun was out and and there was just a tiny bit of wind. We knew upfont that scarf, beanie and gloves were mandatory. Especially at the more windy sections like up top the hills. The view was absolutely terrible, but we made the best of it.
With the sun shining on us during our lunch break at a forest edge bench, we still enjoyed the lookout in 01. I brought some old carpet scraps to sit on and was happily surprised that they isolated even better than I had hoped for. Some hot tea helped us staying warm.
After five hours we returned just after sunset. Iām quite tired now, completely out of shape.
(#6acyh5q) @lyse@lyse.isobeef.org (At least I didnāt break all the links again. In late 2015, I switched from a PHP backend to the current static website, which changed just about everything. I hope doing a disruptive change like this one every 10 years is tolerable. š )
(#6acyh5q) @lyse@lyse.isobeef.org Oh, right. Forgot about that. š«¤
(#6acyh5q) Well, the Atom feed entry IDs changed, too. I had to mark everything as read again.
(#i6mgd3a) @movq@www.uninformativ.de I still think that your original domain is cool as fuck! :-)
I didnāt change any subscriptions, and I still see your messages, so whatever you did worked fine. :-)
(#i6mgd3a) Did it work? Am I still here? š¤£
(#i6mgd3a) @prologic@twtxt.net I think I found an easy way to redirect anything except the twtxt stuff. Thatās probably better. š¤
(#i6mgd3a) @movq@www.uninformativ.de Right š
So, are you guys up for an experiment?
Iām really not happy with the domain āuninformativ.deā anymore. Iām going to switch to āmovq.deā soon (or maybe something else if I get another fancy idea).
If I keep the url = field in my twtxt file, nothing should break, right? Right? š¤£
(#m4r2yzq) @prologic@twtxt.net Yup. š
Fark me OS Dev is hard š¤£
(#hddm6pa) @lyse@lyse.isobeef.org Thanks!
(#qpsyz6q) Wow, as I anticipated, this is waaay out of my capabilities to really understand it. But Iām quite happy to just have spotted a mistake in an explanatory comment in section 4.5.2 āThe icode Arrayā. Of course, it should be /e + tc + /i + ni + t\0. Letās hope that my e-mail with the patch actually makes it into Briamās inbox. I fear GMail just hides it in the spam folder.
(#bkzrqsq) @bender@twtxt.net gemini-cli, something something https://github.com/google-gemini/gemini-cli/issues/16723
I recently got an email with this byte sequence:
\xf0\x9f\x8e\x81\xf0\x9f\x95\xaf\xef\xb8\x8f
Thatās U+1F381, U+1F56F, U+FE0F. The last one is a āvariation selectorā:
https://unicodeplus.com/U+FE0F
My toolkit renders this incorrectly ā and so do tmux and GNU screen.
Unicode aināt easy. š„“
(#qpsyz6q) @movq@www.uninformativ.de Just 323 pages! Thatās cool, letās have a look. :-)
(#hddm6pa) @prologic@twtxt.net Tada! Maybe one day I might look into this lowlevel stuff, too. But I canāt see it on the horizon yet. Happy hacking! :-)
https://github.com/unix-v4-commentary/unix-v4-source-commentary
A comprehensive, line-by-line commentary on the UNIX Fourth Edition source code (released November 1973; tape recovered from June 1974 distribution).
(#hddm6pa) @prologic@twtxt.net Iād love to take a look at the code. š
Iām kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (µ)? š¤
Canāt really answer that, because I only made a working kernel for 16-bit real mode yet. That is 99% C, though, only syscall entry points are Assembly. (The OpenWatcom compiler provides C wrappers for triggering software interrupts, which makes things easier.)
But in long mode? No idea yet. š At least changing the page tables will require a tiny little bit of Assembly.
(#hddm6pa) Iām kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (µ)? š¤
(#hddm6pa) Iāve only got a handful of syscalls working right now. Taking inspiration from the calling convention of the Linux kernel and even made the service/interrupt handler int 0x80h 𤣠Iāve only got read, write, alloc and exit working righ tnow š„²
(#hddm6pa) @movq@www.uninformativ.de Yes!
Did you do the whole dance with BIOS boot and everything?
Yup! Farkān LBA shit and all, loading up the GDT, TSS and switching to x86_64 long mode š¤£
(#hddm6pa) @prologic@twtxt.net Damn, nice! I know exactly what you mean ā the output/screenshot looks trivial, but thereās so much going on behind the scenes. š
Did you do the whole dance with BIOS boot and everything?
(#hddm6pa) Whohoo! š„³ You have no idea how great a feeling this is! This includes the Mu stdlib and runtime as well, not just some simple stupid program, this means a significant portion of the runtime and stdlib ājust worksā⢠š¤£
Btw @movq@www.uninformativ.de youāve inspired me to try and have a good āol crack at writing a bootloader, stage1 and customer microkernel (µKernel) that will eventually load up a Mu (µ) program and run it! 𤣠I will teach Mu (µ) to have a ./bin/mu -B -o ... -p muos/amd64 ... target.
Took me nearly all week (in my spare time), but Mu (µ) finally officially support linux/amd64 š„³ I completely refactored the native code backend and borrowed a lot of the structure from another project called wazero (the zero dependency Go WASM runtime/compiler). This is amazing stuff because now Mu (µ) runs in more places natively, as well as running everywhere Go runs via the bytecode VM interpreter š¤
(#f5fb6gq) @kiwu@twtxt.net Always stay positive! š
(#4b4ypwa) @movq@www.uninformativ.de I guess so, yes. I read something about that in some ticket. In v3 the terminfo support was dropped, though. Iām still on v2 at the moment.
(#4b4ypwa) @lyse@lyse.isobeef.org ⦠I sure hope that they generate these files from the general terminfo database instead of maintaining their own DB. š³
(#4b4ypwa) And tcell seems to support my urxvt in general: https://github.com/gdamore/tcell/blob/v2/terminfo/r/rxvt/term.go#L144
(#mqvmwva) @movq@www.uninformativ.de Woah, thatās really amazing progress! :-)
(#mqvmwva) @bender@twtxt.net Iām already using it for tracktivity (meant for tracking activities and events, like weather, food consumption, stuff like that), which is basically a somewhat-fancy CSV editor:
https://movq.de/v/f26eb836ee/s.png
I have a couple of other projects where I could use it, because they are plain curses at the moment. Like, one of them has an āedit boxā, but you canāt enter Unicode, because it was too complicated. That would benefit from the framework.
Either way, itās the most satisfying project in a long time and Iām learning a ton of stuff.
(#4b4ypwa) @movq@www.uninformativ.de Yeah, I know that terminals are super weird and messy. In both the KDE Konsole (identifying itself as TERM=xterm-256color) and xterm (TERM=xterm) it just works flawlessly. My urxvt (TERM=rxvt-unicode-256color) just doesnāt. I also tried messing with TERM in urxvt, but no luck so far.
(#4b4ypwa) @lyse@lyse.isobeef.org Unix terminals are quite limited in that regard. 𫤠You know how Ctrl works? The XOR 0x40 thing? And Alt doesnāt exist at all, itās just a prefixed ESC byte.
I was surprised to see curses knowing about āShift+Tabā, wondering how that is supposed to work. Well, itās an escape sequence, of course (depending on the terminal, of course).
(#4b4ypwa) Well, in Xterm, I actually do get key combinations with the Shift modifier. Also, combinations of several modifiers just work exactly as I expect. But not in URXvt. Hmm.
Here am I looking at the different tcell.Key constants and typing different key combinations in the terminal to see the generated tcell.EventKeys in the debug log. Until I pressed Ctrl+Alt+Backspace⦠:-D Yep, suddenly there went my Xā¦
So far, it appears as if I can have either only Ctrl or Alt as modifiers. But not in combination. And Shift is just never ever set at all. Interesting.
Some work on the menu system to brighten my mood a little bit. No mouse support yet.
(#ajerg7a) @prologic@twtxt.net Probably not, but thanks. š Itāll get better.
(#ajerg7a) @movq@www.uninformativ.de Anything we can do? Lend a listening ear? š
(#ajerg7a) @prologic@twtxt.net Work and the general state of (gestures broadly) everything.
(#ajerg7a) @movq@www.uninformativ.de Whatās up? hmm š§
Frustration level: Through the roof.
(#sczoyta) Ha, I just stumbled across https://codeberg.org/tslocum/cbind, perfect!
(#r7dvytq) @bender@twtxt.net ICQ, yeah, I vaguely remember these times, despite I still know my ICQ number like it was yesterday. :-D
@shinyoukai@neko.laidback.moe No, itās not dead. The one account in question actually is on jabber.org.
(#zqzv6cq) @bender@twtxt.net I vaguely remember this, some leftover from the old-style hashtags? The (#foo) stuff? š¤
Heh I thought I fixed that bug? (is it s abug?!)
(#2puspya) @lyse@lyse.isobeef.org Never heard of either, tbh. š³
This week, Mu (µ) get s bit more serious and starts to refactor the native backend (a lot). Soon⢠we will support darwin/arm64, linux/arm64 and linux/amd64 (Yes, other forms of BSD will come!) ā Mu (µ) also last week grew concurrency support too! š¤£
@klaxzy@klaxzy.net nothing like a blank twt eh? š