I've been testing how nice it would be to use man.sr.ht for
documentation for my OS project. I have an article in place of
a source file and I'm almost fully satisfied.
Article in question: https://man.sr.ht/~samhsmith/AstraOS-wiki/src_tree/src/elf.c.md

As you can see in the article there are two subheadings called
"Members". Each one refering to the struct members of the struct
described in the heading above. If you click the Members section
in the table of contents you will go to the first. This is because
the link generated takes only into consideration the name of the
heading. While it is probably unwise to have the links be numbered,
ex Members and Members2. Having the links generated include parent
heading would allow me to link to the two Member sections
independently.

> No worries at all, and you aren't alone 😉 sorry to bug
All emails are very appreciated. Being seen is motivating.
--
Sam H Smith

Yea I'm aware of it. If I recall correctly it was a minor name clash compared to some other names I considered. Putin doesn't market Astra Linux very heavily.

Feel free to throw some other names my way. You never know, there might be a rebranding some day.

(Sorry about the double (now triple :( ) email xstefen, still getting the hang of mailing lists)

AstraOS v0.2 is finally here!

What things are new from version 0.1? Well, in no particular order,
* Streams aka Fifo's
* A terminal called dave_terminal
* Multicore support
* User Threading api
* Thread Groups
* Inter Process Function Calls aka IPFC's
* Two gui-app api's built with ipfc's
Going along with the new features are of course fixes to the many 

bugs I found in previous versions. Playing around with this version

AstraOS v0.2 is finally here!

What things are new from version 0.1? Well, in no particular order,
* Streams aka Fifo's
* A terminal called dave_terminal
* Multicore support
* User Threading api
* Thread Groups
* Inter Process Function Calls aka IPFC's
* Two gui-app api's built with ipfc's
Going along with the new features are of course fixes to the many bugs I found in previous versions. Playing around with this version is a whole lot more fun then v0.1, it's almost exponential the effect of adding more to an Operating System. We still have a very long way to go though. The next obvious thing for me to work on is the file api. Right now you can only launch new programs from files and navigate a directory structure. Once you can read and write files, the core pillers of the OS will exist. Graphics, User Input, Inter Process Communication, Persistent Data Storage. That's something you can start building on top of.

Tutorial videos and articles concerning all features will be made over the coming weeks. If you have any questions or would like some help concerning AstraOS, do email me at sam.henning.smith@protonmail.com.

Whoops, forgot to wrap my lines properly.

There is now a pre-pre-alpha of AstraOS for people to try. For instructions
on how, please visit,
gemini://samhsmith.net/blog/astraos_tutorial_from_nothing_to_window_with_colours.gmi

The next thing I will be working on is Streams, as to avoid the current hackery
required for printf. Then after that I will be implementing multithreading. This
will allow me on my machine to get 6x-12x the performance. Which should help
a lot with delivering 1080p@60hz cpu render on an emulated system.

There is now a pre-pre-alpha of AstraOS for people to try. For instructions on how, please visit, gemini://samhsmith.net/blog/astraos_tutorial_from_nothing_to_window_with_colours.gmi

The next thing I will be working on is Streams, as to avoid the current hackery required for printf. Then after that I will be implementing multithreading. This will allow me on my machine to get 6x-12x the performance. Which should help a lot with delivering 1080p@60hz cpu render on an emulated system.

Fantastic!
I got it working now. Many thanks.
Feel free to keep sending patches. And don't
hesitate to ask me if anything about the code is
unclear.
--
Sam H Smith

> Did what you piped into git am include the headers, or was it just the
> body?
I used the pipe function in my email client aerc. I ran :pipe git am, here's it's description.
       pipe [-bmp] <cmd>
           Downloads and pipes the selected message into the given shell command, and opens a new terminal tab to show the result. By default, the selected
           message part is used in the message viewer and the full message is used in the message list.

           -b: Run the command in the background instead of opening a terminal tab

           -m: Pipe the full message

           -p: Pipe just the selected message part, if applicable

> > Are user.email and user.name defined properly?

I piped it straight into git am.
What does git config -l report while inside the repo?
Are user.email and user.name defined properly?
--
Sam H Smith