operating system development - terminal scripting

[00:00:08]Okay, we're back.

[00:00:12]Good. My computer just [ __ ] froze on me completely and utterly 100% cuz this is a thing that again can happen on Linux.

[00:00:22]Uh, cool. [sighs] Cool.

[00:00:35]Love that for you. Linux [snorts] de G. What is that?

[00:00:49]I am now live. Terminal scripting. Yep, that's what we're doing. Um, by any chance did I just keep this running?

[00:01:00]Cuz that's the only thing I can possibly think of. For some reason, this script is just making my uh my system go crazy.

[00:01:12]And it probably just like I don't know. That's the only thing I can possibly think of.

[00:01:25]Uh anyway, uh most likely [sighs] ridiculous ridiculous behavior, man. Uh if it is that if this script for some reason just caused an infinite loop, why is it allowed to take over my entire system like that?

[00:01:48]Linux, is this not a thing? That can be very very problematic.

[00:01:53]Isn't this just denial of service like waiting to happen? I don't understand how Linux is not more exploited as a system cuz like genuinely stuff like this doesn't even require malware. It's just Yeah.

[00:02:11]Anyway, um packager.

[00:02:27]All right. So, I did this thing, this macro here.

[00:02:42]You can delete your root folder if you want. We're not going to stop you if you really want. They do stop you now.

[00:02:49]Um, they do stop you now. You need to use uh no preserve root if you want to do that. I did do that in a virtual machine in BSD and in uh one of those very simple Linux distros.

[00:03:08]I don't remember which one. One of the very uh user friendly ones. So I did do it on some virtual machine.

[00:03:16]But no power didn't go out. Um, the working theory is that for some reason the script that I was writing just took over the entire system, froze it completely, and I couldn't even access the little emergency terminal thingy to kill it.

[00:03:34]Cuz apparently this is not a thing that Linux has considered.

[00:03:39]Denial of service should be so [ __ ] easy on Linux, by the way.

[00:03:46]It seems so easy.

[00:03:49]But mind you, um, you know, all it takes to do a little denial and service attack in my system HTML tag.

[00:04:00]I'm not one to talk, but to be fair, that is uh intentional behavior that I did with uh the crossplatform version will not crash your system. It will just show you this and then halt your program.

[00:04:19]Um, the operating system version of it is going to panic your system with this message.

[00:04:32]I have no idea what I did to break the system like that. Again, my working theory is that this very innocent script that I was writing somehow ended up in an infinite loop because I'm changing the path. That's probably what's happening.

[00:04:47]Anyway, um I have another red lisp, by the way, which is a library. That's not the name of my lisp.

[00:05:05]I have a little utility here.

[00:05:09]Wait, does it use red lisp?

[00:05:14]No, it doesn't.

[00:05:16]Okay. So, I'm not I'm not going to use red lisp. Uh I'm just going to put the macro in here.

[00:05:24]Um or essentially, we're going to tmp switch directory, right? To temporarily move you inside of another directory, then run some code, then move you back to the old directory.

[00:05:46]And we're going to do a tmp switch deer into the path.

[00:05:57]In there, we're going to run red build and [sighs and gasps] we should go back. Bye, Gen Noob. Thanks for joining. Thanks for the raid.

[00:06:17]All right. Um, that is the plan for this thing.

[00:06:21]By the way, if this works, I'm going to put it here. Although, that goes in FS.

[00:06:25]So, 100% just move it in here.

[00:06:28]Anyway, this is the operating system, which I don't need right now.

[00:06:33]So, I'm working on the operating system from outside the operating system. All right. If the stream goes down again, we can confirm my theory.

[00:06:43]This time it seems to have worked at the very least kind of somewhat.

[00:06:48]Um, it didn't do that whole thing. So, that's good.

[00:06:58]But I need you to recompile undefined reference and undefined reference to ripple run.

[00:07:21]Okay, so it didn't work because it didn't recompile the compiler. Ironic.

[00:07:29]Um, that should have been quick. That should have been a quick little detour that I was taking to do this very quickly and then um go back to what I'm actually doing.

[00:07:43]Somehow that didn't work.

[00:07:47]Anyway, let me uh very quickly print the uop um get cwd.

[00:08:01]So, print the current working directory.

[00:08:05]Do that.

[00:08:11]Homed beyond home d uno. So, it should be trying to run the command called redu build.

[00:08:20]Is that a problem?

[00:08:23]It's probably a problem. Yes, because that's not a real command. That's just an alias.

[00:08:34]No, it is a command. So, it is a bash script. So, maybe it doesn't run it properly. Anyway, I'm just going to run the command like this.

[00:08:49]Still didn't do it.

[00:09:04]There's no reason why this can't just be a function. by the way.

[00:09:16]Yep.

[00:09:18]Okay. The second I saw it hesitate a little bit take a little bit longer, um, I froze it. But it is working. Okay.

[00:09:28]I saw it take a little bit too long and I was like, "Oh, oh god, it's going to happen again." But no, we're good. That actually worked. Okay. Why are you streaming at 60 fps? Oh, you need to see me moving smoothly.

[00:09:44]And the dog, you need to capture the the movement of the dog. He's like a very active dog actually when he's not at home.

[00:10:02]We're filming a nature documentary where you need to like see the the cheetah running in in in slow motion. So that's why I'm I'm doing 60 fps except the cheetah is actually a cow that's asleep on the couch on the bed.

[00:10:22]All right. Um so that detour was a little bit more destructive than it was supposed to be. I still don't understand how this could possibly have led to an infinite loop and how Linux possibly allows something like this to take over your entire system. Again, the Nile service should be really, really easy on Linux. But anyway, a fork bump fork bump.

[00:10:48]Anyway, I can now recompile my dependencies without needing to uh do it manually because I've been forgetting to do that and then being like, why doesn't it work? Why doesn't it work? Okay, so it didn't recompile.

[00:11:05]Um, and yeah, um, issues aside, adding new features to something in Lisp is incredibly simple. I have to say possibly the thing that I like about Lisp is the same thing that I like about Emacs is the same thing that I like about Unix.

[00:11:26]Um although I don't like Emacs and Unix, there are two things that I like about them. The fact that everything in Emacs is treated like a text buffer and the fact that everything in Unix is treated like a file. I copied both of these philosophies in my own text editor and my own operating system for a reason.

[00:11:44]And I do like lisp, but even then I made my own lisp.

[00:11:49]I think it's the fact that the entire thing works off of one single philosophy.

[00:11:58]Everything is standardized to work in the exact same way. Everything is a file. That means every resource in the operating system is mappable or mapped to a file.

[00:12:12]What does this mean? Using file system operations, two completely incompatible well, two completely separate systems can be made to talk to each other.

[00:12:24]Uh, which is a pretty cool thing. Plan 9 handles that masterfully. Unix and Linux and Mac don't take this super super far.

[00:12:33]my system should but honestly there's a lot of resources that I haven't mapped to the file system that I should like for example graphics I figured what's the point but yeah there is a point if you want to print to the screen using the file system you should be able to there is a standardized interface to do anything in the file system any resource in the in the operating system um standardized to the file system which allows you to do things like again two incompatible pro uh programs talking to each other.

[00:13:09]Uh distributed distributed operating system. How do you do that? Through the file system.

[00:13:15]Um even the way that I did like interprocess communication. How do you do that? Through the file system.

[00:13:23]Simple as that.

[00:13:26]Emacs does the same thing with text buffers. So everything is a text buffer.

[00:13:32]So, um I I mentioned this yesterday, how two plugins that you use in Emacs can be made to talk to each other. Like you can use a multi I believe Zozing made a video on it where he used multicursor in the EMAC shell or another program. I don't know if it was the Emacs shell to mass rename files because the shell program allows you to run ls and then rename the files from the list directly and multicursor allows you to edit multiple lines at the same time.

[00:14:11]You can mass rename files that way.

[00:14:15]Uh again you can make incompatible or completely separate programs or completely separate um plugins of your code editor a text editor talk to each other because they use the standardized interface and likewise in lisp everything is a list. So you have again the standardized interface way of doing things which means that anything that is a sequence of things can be made into any other sequence of things which guess what most things are sequences. Do not say all things are sequences. So that's what I think makes me really like lisp the fact that in lisp just like in Everything is a file file system uh file systems and textbased editors like Emacs. You have the standardized interface through which everything can be made to talk to anything else. Pretty cool. And now I have a lisp, a textbased text editor and an everything is a file operating system. So the interconnectivity between them should be out of this world. I guess we'll see.

[00:15:36]All right. Can we actually run this thing now? If I try to run uh ls as a lisp command symbol not found ls tries to get a fallback, but of course the fallback doesn't actually work.

[00:15:56]So there we have it. Still using zed.

[00:15:59]Still using zed. Yeah.

[00:16:03]Um, yeah, it's fine. It works.

[00:16:12]Um, I'm still using Z for now because the code editor, uh, right now I'm using it as a terminal. So, I'm not doing a whole lot of work on the text editing part.

[00:16:23]But um for the time being, we're going to be using Zed for a little bit. Honestly, until I add multicursor to this thing, I don't see myself using it all that much.

[00:16:36]I use multicursor way too much to not have it.

[00:16:41]Okay. Uh so the first thing I want to do is I want to change some code up. Well, actually expose explode. Expose expose some code from list interpreter.

[00:17:11]This one is the main one that I need right now actually.

[00:17:15]So that it's also available both static inline with static inline.

[00:17:22]Okay. No, it's not anymore.

[00:17:25]I do need it. Well, I can still make it static inline. [ __ ] it. Just put it out here.

[00:17:36]Uh, so I can use it outside here.

[00:17:39]And car ID for the expression that will give me the command that we're trying to run.

[00:17:49]Quick and easy. and convenient.

[00:17:58]Um, this returns a string slice. Yeah.

[00:18:02]Run command V and then tell us the command that you're trying to run. All right. So, let's see how that works.

[00:18:12]ls.

[00:18:15]See, there are still bugs in this thing like a lot.

[00:18:20]All right, it wants me to run the ls command, but it's not actually running it yet. Okay, we're good.

[00:18:27]Uh, have you read the C programming book? If yes, how did it help you learn the C language? I have not. I learned the C language by writing the C language. I believe that's the best way to learn a language.

[00:18:45]The only book I ever considered buying for programming was the lift book.

[00:18:51]This one um I never did it. [snorts] Mostly because I like the cover. That's the only reason.

[00:19:07]Anyway, uh by the way, my idea of moving myself over here is just leaving an empty gap down here now, which is really ridiculous and hiding the dog.

[00:19:18]And also, it's uncomfortable as hell.

[00:19:20]So, uh probably tomorrow I'm going to be back to my regular setup, which means I need to move my monitors again. Oh my god.

[00:19:29]Oh well. All right. So, we know what command we want to run. Uh we have the arguments of that command. Here's the kind of ugly part of this is that the run command um implemented by the shell calls command input on the actual shell shell run command. So my shell actually calls this function and this function can just move your camera. No, it's about moving myself mostly cuz yeah, there there's nothing on this side of the room to show. The only slightly interesting part of the background is that one. Then there's this whole empty space there, which I always found very annoying, but there is the dog on the bottom part of that. But no, most likely I'm going to go back to my normal setup.

[00:20:35]Um, [snorts] although I do have to say the monitors like this make more sense.

[00:20:45]I'm going to try something during the next ad break, but not right now.

[00:20:50]Anyway, uh yeah. So, the thing is that like the shell processes its own arguments and it kind of sucks, but it means that I have to take the already established list of arguments from here and flatten it, turn it into a string and pass it in to be parsed.

[00:21:35]So that would be very ridiculous, but it is the best way that I can handle this right now.

[00:21:48]I still don't know even where I want the scripting to live. Right now, it lives completely outside of the shell, which itself is pretty ridiculous. I don't want it to live within the shell because then that would mean uh making the uh library that the shell lives in have a dependency which is not allowed to have.

[00:22:16]So yeah, I need to figure all this out. So, for now, I'm okay with like I'm going to have to take this, turn it back into a command, parse it into a command, and then handle that. I don't know. If you move your camera to the right side and pointing to the other desk for a better angle, you would be fine.

[00:22:42]Uh, camera over here.

[00:22:47]And pointing No, I think camera over here and pointing that way is what you mean.

[00:23:12]But I'll figure it out. I'll see you later or tomorrow.

[00:23:19]Unfortunately, uh I I will be periodically moving aside so you can see the dog.

[00:23:28]You move us to the left to looking more to the right side.

[00:23:32]So yeah, what I said. Yeah.

[00:23:35]Yeah. Uh that that could work. That could work. I'll I'll figure it out tomorrow.

[00:23:41]Uh or during the adbreak. I guess I'll figure it out.

[00:23:45]Uh, the DRO is Hannah Montana Linux.

[00:23:52]All right, this is going to be very ridiculous, but anyway, we're going to run this command and we're going to run it with these arguments. Now, the arguments we're going to have to flatten a little bit. Uh, so before I do that, I'm going to print the arguments, see what they look like. We don't have any arguments right now, so that's very convenient.

[00:24:11]But let's say that we do have arguments like ls.

[00:24:15]Actually, let me try this. Add one, two.

[00:24:21]Oh no, that's not what I was expecting at all.

[00:24:27]Oh no, it does not work like it was supposed to.

[00:24:33]You were supposed to first evaluate the arguments.

[00:24:42]Let me see real quick.

[00:24:56]Yeah. This does not evaluate the arguments first.

[00:25:01]Uh, so it needs to do that which if I'm not mistaken, Eval does. So I can copy that EIS.

[00:25:23]evaluating the list of arguments which are a using the environment m.

[00:25:32]What's your problem?

[00:25:43]Got to move it up.

[00:25:50]All right. So, that should evaluate the arguments. At the very least, it should tell me to run command ls3. That's what I expected to see there. Not add one, two. There should be no lisp in that in that whole thing.

[00:26:04]No, still didn't work.

[00:26:11]Which is actually surprising. You were supposed to evaluate.

[00:26:16]There's no way you couldn't evaluate the symbol.

[00:26:29]There is a fallback though in which you evaluate this value.

[00:26:50]All right. Is this working?

[00:27:27]The evil result is three.

[00:27:40]Wait, I don't understand what's happening here.

[00:27:47]The value that it's doing is this one.

[00:27:52]It should be ls with three.

[00:27:57]Run command.

[00:27:59]Oh my god, I didn't put in this thing.

[00:28:04]I'm checking an argument that isn't actually there. My god, this keeps happening, by the way. Second time it happened today.

[00:28:17]Oh, that looks better.

[00:28:21]Wait, no. Cuz I'm being so dumb right now.

[00:28:32]Obviously, you don't print this code gen type as if it was a slice, a string slice. That makes sense. But I was already printing it here, which is why this was here, which means it was working.

[00:28:47]God, I just put them in the wrong order, so I couldn't really understand what was happening.

[00:28:53]Oh my god, that was ridiculous.

[00:28:56]Add one, two. I'm pissed off of myself right now. [ __ ] sake. All right. Uh, so run command ls with this argument.

[00:29:06]Cool.

[00:29:08]And then the ripple is printing the result, which is nil right now. It's fine.

[00:29:19]ls add one two.

[00:29:22]All right. Wrong command ls with this argument. That's it.

[00:29:26]All right. We're good. We're good. We're good. Jeez, that was stupid as hell.

[00:29:32]Anyway, um yeah. So, we have to take this thing and convert it into a string. Although again, ls is not a command that has uh a numeric argument.

[00:29:48]It can have arguments, but it usually you don't use it with arguments cuz you're trying to get it for the current directory. You can of course you can get um how about OS? You can list the contents of another directory by doing this. It's just not a very common thing.

[00:30:12]I was doing numeric because um I needed to test evaluation of symbols and also uh these two I need to press shift to press to do them and I'm pretty sure my UI library which is the one that handles the input into the buffer uh does not actually handle modifiers. So I may add that in a minute but I don't have it right now. I don't really need it right now. Uh what I need to do is take this thing and flatten it into a string.

[00:30:49]All right. So we can do string return a string of uh sex to string.

[00:31:10]Sex of course being sex as expression not sex expression.

[00:31:19]I always call it a sex expression. I'm not really I'm not trying to be funny.

[00:31:23]I'm not trying to be edgy with that. I literally am just unable to pronounce things properly.

[00:31:35]an S expression.

[00:31:43]Uh, no, not not that. It's a string slice.

[00:31:47]If no cmd data or no cmd.length, return an empty string.

[00:31:59]All right. Then um the code gen here is going to be a linked list of Hold on.

[00:32:15]Check it real quick.

[00:32:29]a linked list of arguments to the function. Right? Let's say that I do ls la which I am allowed to do and then I do home doos.

[00:32:50]I do have to stringify them. It would be nice to be able to not do that, but I do have that right now.

[00:33:04]Yes. Okay. So, I just need to flatten this list into a string pretty much.

[00:33:18]Just join your Oh my god.

[00:33:21][laughter] I am so sorry. I was about to ban you because I read join our Discord. I was like, "No, don't don't be advertising stuff." I'm sorry. You said join you.

[00:33:32]Join your Discord. Okay. Welcome. And I'm sorry.

[00:33:37][laughter] I read that way wrong. Welcome to my Discord.

[00:33:45]Anyway, um yeah. So, uh the list looks like this. and we're going to need to flatten it.

[00:33:52]Um, essentially we should be able to get the first argument with car just car which is another function that is not exposed.

[00:34:14]I'm going to do that real quick.

[00:34:28]if I could find it.

[00:34:30]All right, car CDR cons. All of you, you're moving to the header. You're already static in line, so might as well. Who gives a [ __ ] Is Adam, too?

[00:34:39]Apparently, it's needed.

[00:34:43]Wait, why is this one not static in line?

[00:34:48]You you you these ones I actually do want them to inline when possible. So anyway, uh get the first argument of the args and see if that can be printed.

[00:35:36]Yeah, I don't need to do this right now.

[00:35:38]I I know it works.

[00:35:40]Definitely.

[00:35:44]All right. So, take that equal to that thing.

[00:35:56]And then, wait, hold on. Let me be smart about this. Let me use a buffer.

[00:36:11]All right. So what I'm going to do is I'm going to do buffer write into this buffer the command data with a command length.

[00:36:24]All right. So that gets written.

[00:36:28]Then I do have to manually write that that sucks to do it like that but okay it works. Settling for lisp. Excuse me.

[00:36:44]Settling for lisp. What?

[00:36:48]I am choosing lisp. It is my first and only choice. It's not the last choice.

[00:36:52]I'm not settling for it.

[00:36:56]Okay. So, we're going to get the car and can we make this uh already recursive?

[00:37:11]Right, it should be possible.

[00:37:14]So, do this while we have an args pointer.

[00:37:22]while that exists or actually um while that exists immediately do it like that. Okay. So get an argument if the argument doesn't have a pointer for the car uh or um it is not the correct thing which is a lisp value code. uh s rule lisp value which should be called atom but somehow it's called that then we break out of this whole thing.

[00:38:01]All right. Um if the argument is no actually we don't need to check the value of it.

[00:38:19]No, we do. We do. We do it.

[00:38:24]Take that. Then switch switch on the uh code type and populate the switch for me. Thank you. That is utterly useless. Why?

[00:38:45]I don't know why both Zed and Clang are breaking or clang within Zed is breaking or Zed is just breaking but both of them are starting to get worse and worse and worse.

[00:38:57]Um, so yeah, that was not C++ code. I can tell you that much.

[00:39:06]Um, hello Rudy. There's the dog.

[00:39:17]Yeah, that is the main re reason why moving over to this side is not working out. He is the main reason for that.

[00:39:25]Uh him not being there anyway. All right. So if it's a nil or true value, then in that case we don't do anything.

[00:39:35]We continue. Well, no, we don't continue.

[00:39:38]We break out of the switch.

[00:39:43]Uh in case it is a numeric value, we are going to print it to the buffer using a buffer right into the buffer where we put in all this stuff using that and a space at the end. And the value we're going to take from val, no, from number.

[00:40:09]Right now I only support um integers by the way which is not great but whatever.

[00:40:19]Okay that and then break.

[00:40:22]So we're going to be taking these and just um formatting them otherwise there is a val.

[00:40:35]But when something is a string, we actually need to turn it from a string into a normal argument. Right? If something's like this, then it's just period.

[00:40:51]All right? So that is going to be um done with a substring. We're going to check if code val length is less than two.

[00:41:06]then break because it's not long enough to do what we need to do. Otherwise, we're just going to create a string slice out of this one + one and code val.

[00:41:22]Did you cry length minus two? You're good, Jester.

[00:41:28]All right, at least you can see him now over my shoulder.

[00:41:31]I just need the devil over here. or an angel. He's depends on what he is.

[00:41:41]Are you reading any books at this moment related to programming or in general?

[00:41:50]Um, of course, this gets printed as a string slice skipping the uh quotation marks.

[00:42:00]And in the case of an identifier, we just straight up print it as is break.

[00:42:19]All right. I'm doing nothing with this, by the way. I need to return the buffer. I'm not using a string. I'm using a buffer now.

[00:42:31]So just return the buffer. Who cares?

[00:42:40]It is being created. So no. Okay. Let's do it like this.

[00:42:47]So So return an empty buffer. If there was an error, you don't have a command.

[00:42:52]Uh otherwise return the buffer.

[00:42:56]And now here the command that we're going to run is actually going to be taken from sex p to string using the expression and the arguments.

[00:43:09]Let's see what that looks like.

[00:43:16]ls home do my home directory whatever. And then also la. That's probably not the right order, but we're still not executing the command, so who cares?

[00:43:32]Uh, that looks like it did nothing. Oh god. Oh god. Oh god.

[00:43:41]Oh, why are you trying to terminate? I already did it, didn't I? Why is it still running?

[00:43:50]Why is it still running?

[00:43:58]Linux, what the [ __ ] I told you to terminate it twice already.

[00:44:04][ __ ] Am I doing something wrong here? Like what what am I supposed to do here?

[00:44:47]The process is not running anymore.

[00:44:56]The process is actually not running anymore.

[00:45:01]Why won't this go away, bro?

[00:45:09]It still won't close it.

[00:45:20]the process being controlled by the image uh SPCL already quit mind you I understand why it doesn't quit the process kind of but genuinely the process is not open anymore according to top according to PS and according to the fact that I cannot close That what is that?

[00:46:12]I also cannot kill it.

[00:46:19]I created a zombie. Sure, but I cannot kill it at all. Also, how the [ __ ] did I do that? This is the most I keep doing the most basic things in Linux and breaking everything. That's just a sign that is a bad system. Like, what the [ __ ] is happening? Anyway, at least I figured out the name of it is actually rain though I cannot find it.

[00:46:47]Oh, there it is.

[00:46:49]Okay. But the process name doesn't actually it doesn't let me kill it because it says that it doesn't exist.

[00:47:04]Um, I do understand this is a big limitation of my s of my build system. Actually, this is 100% its fault. Um, I'm just checking that it's not using too much memory, you know.

[00:47:44]I no longer see it in the list of processes. Oh, it's gone.

[00:47:49]It's gone. It's gone. Holy [ __ ] Okay. Well, whatever the [ __ ] just happened. I don't know. Let's maybe sort out our process [ __ ] a little bit, Linux, cuz I I can't believe that Linux has the same issues that my system has when Linux is older than me.

[00:48:16]Not older than my system. It's older than me. How is that possible?

[00:48:28]I don't get it.

[00:48:33]Anyway, the reason that entire thing happened is that I am never moving the cursor of args to the next one.

[00:48:58]Let me reopen the terminal real quick just in case I need it.

[00:49:09]Jesus Christ, man. That was ridiculous.

[00:49:32]I feel like it was doing it again. No, it didn't. It didn't. It didn't. It just uh didn't return any value.

[00:49:43]All right. Um, how about I print them real quick?

[00:49:52]All right. So here I want to print the code val.

[00:49:59]Here I want to print the code val.

[00:50:05]Here I want to print the code number.

[00:50:10]No, I want to debug print them otherwise it's going to spam too much.

[00:50:18]All right.

[00:50:29]I don't really care what I put in here.

[00:50:35]LS a a Oh.

[00:50:41]Oh, I'm just trying to print the buffer as a string. That won't work. Um, all I have to do is slice from buffer.

[00:50:52]But that does mean I need to take the command like this.

[00:51:04]Do this.

[00:51:16]All right. LS A that crashed.

[00:51:30]Um, okay. So, the number didn't work. Oh, wait. [sighs] I forgot to change the format type here.

[00:51:39]Literally, my debugging is what bugged it.

[00:51:42]It's call me GDB. The way I'm able to just do that.

[00:51:51]All right. Uh, that is not correct.

[00:51:54]Kind of not correct.

[00:51:58]It's kind of correct.

[00:52:02]It did a a just what are you trying to evaluate is the question. Where does this evil null pointer come from?

[00:52:16]Symbol not found. Aa Oh, right. I Okay, that's where that came from.

[00:52:22]Um, so I can't use an identifier if it doesn't actually exist. That makes sense.

[00:52:34]ls aa123.

[00:52:40]All right, wrong command. LS aa 1 2 3.

[00:52:42]Okay, so it works. But I did forget.

[00:52:47]I literally said I have to write uh arguments in this very ugly manner, like spaces in this very ugly manner, and then I never actually added a space.

[00:52:57]But anyway, we're just going to do it like this. Screw it.

[00:53:12]All right.

[00:53:23]Okay, cool. That's the command that I'm trying to run. ls aa1234.

[00:53:29]Again, I would love to be able to do a little bit of hacking magic for paths without needing to use strings for them and maybe even arguments like these so that you can just type them immediately.

[00:53:44]Um, but again, we haven't actually designed the lisp uh dialect that this whole thing will be using. It's an incredibly limited way of working. But we are now able to run this slice and that means string slice strng string slice s. And now, um, I do realize we also need to pass this into it cuz that contains the shell that we're going to be talking to like that.

[00:54:50]And this function [sighs and gasps] needs a void context which is not possible for us to get. Oh my god.

[00:55:10]Never mind. Let me do it another way.

[00:55:44]That sucks to do, but yeah.

[00:55:49]Umh.

[00:55:52]All right. So essentially we'll just assign this context thing before we do the ripple call so that uh when we get here we'll already have it here and we can run this.

[00:56:07]Sucks but we don't have closures.

[00:56:14]Uh we also need to check if there's no current buffer we return a nil expression.

[00:56:21]And we also return a nil expression in general, but we could return a true or false, right? When we run commands, that would be cool to do.

[00:56:34]Um, right. There's already something called current buff shell context. Let's call it that.

[00:56:55]Now we can do ls la unknown option la usage ls path.

[00:57:12]This is this is my built-in ls function.

[00:57:15]I forgot about that. It's built into the shell. Uh, so I'm not using the um the normal ls that actually takes LA as an argument. There's no hidden files. So it doesn't make any sense and it's always listed. That doesn't make any sense. Are you making a kernel sysol paging management or you building on top of a kernel? So making it but tbh been over a year so it's already pretty advanced.

[00:57:45]Um, so right now I'm not even working within the operating system for that matter.

[00:57:52]Um, for no particular reason. I I probably will before the end of the stream. Why not?

[00:57:58]Yeah, I should have time uh [sighs] to to try and run this thing in the operating system itself. But yeah, it's my own kernel just already built.

[00:58:10]All right, cool. So I actually figured out how to do command runs uh within the lisp script.

[00:58:19]I still again lisp doesn't even live within the shell cannot live within the shell technically cuz all this code is part of a completely different library.

[00:58:30]I would need to either move the shell out of the current uh library that it's in or um which is a possibility actually very very likely possibility or move it elsewhere or something I don't know I'll figure out the code organization but the code works which is the important part I can now write scripts with this thing Now, um, how about we test a command that actually works, like pwd.

[00:59:09]Uh, that's what we're currently in.

[00:59:11]Although, uh, this error still gets printed every time.

[00:59:16]That's not really an error anymore. We do allow for uh unresolved symbols cuz now we allow external symbols.

[00:59:28]So that imaginal fallback function call where I say asuck error.

[00:59:44]I'm only going to print this error if it is actually an error.

[00:59:50]So if I don't have a fallback for it.

[00:59:59]There we have it.

[01:00:01]Random question. If you could, would you live here in Japan? Never been to Japan.

[01:00:07]I'm not sure I would live there.

[01:00:12]Never been, so I couldn't tell you.

[01:00:16]It's not a thing I have considered ever.

[01:00:20]I've considered visiting but not living.

[01:00:23]And again, can you really consider living in a country you've never visited?

[01:00:28]All right. Um, there's an ad break coming up and I'm going to experiment a little bit with my setup without, you know, moving any actual stuff around, but I'm going to see if I can figure figure it out a little bit. So, I'll be back in 3 minutes. uh possibly on this side of the screen. Now Heat. Heat.

[01:01:30][music] Heat. Heat.

[01:01:52]Heat. Heat.

[01:02:01][music] Heat.

[01:02:26]Heat.

[01:02:36]Heat. Heat.

[01:02:56]Heat.

[01:03:16]Heat.

[01:03:45]Heat. Heat.

[01:04:15]All right. I brought this guy since I wasn't able to move my setup.

[01:04:36]So, at least he's here.

[01:04:42]What's up, buddy?

[01:04:46]Um, you're very very warm. It's not very good when it's like 50° outside right now.

[01:04:56]Yeah, he agrees with me. He just pretty much jumped off.

[01:05:00]All right. Um, so what do we have right now? I tried I tried fixing my setup and yeah, this does not work.

[01:05:10]My old setup was way better and I need to just revert it back.

[01:05:15]came here not even knowing Japanese.

[01:05:18]Well, [snorts] I feel like if you want to learn Japanese, that's probably the easiest way to learn it.

[01:05:24]Um, it's pretty much been proven actually.

[01:05:28]Not going to lie, I've definitely tried that with French.

[01:05:33]Not living in France, mind you. Just like forcing myself to speak French whenever I I need to.

[01:05:41]Uh, so well anyway, um, I know a surprising amount of French for somebody who never studied it.

[01:05:53]So, yeah, I'm not doing too bad, I guess.

[01:05:58]How old is he? Uh, he's turning seven next month.

[01:06:08]All right. So, the way things stand right now, first off, I turned my compiler into a library, which is a thing that I genuinely like completely glanced over. It doesn't really matter. It's just literally just changing a compilation flag from B from bin to lib. Literally, that's it. Um, but still pretty useful.

[01:06:32]Um, I made a ripple for it and whenever the ripple fails to resolve a symbol, it will try to use a fallback for that symbol.

[01:06:46]So, we have a scripting language, I believe.

[01:06:54]However, we don't necessarily have the easiest way to write that scripting language to do anything useful with it.

[01:07:03]Uh maybe that's a thing that I I can do tomorrow most likely because right now what I would like to do is to compile this thing for system operative.

[01:07:20]Um although I I do have to say I'm not entirely sure how to do that.

[01:07:29]Um because of this build system pretty much the build system is not prepared to recompile dependencies for the correct system yet. So I'm going to have to do that part manually.

[01:07:49]Oh well.

[01:07:51]Uh let's see if we can first off. All right. Okay. So, you're going to compile for reducted.

[01:07:59]Um the rule gen you're going to compile for the native cuz that's just a dependency of the compiler itself. Then the compiler you're going to compile it for redacted.

[01:08:12]All right. We're also going to need to do the same thing for the UI library.

[01:08:17]My old uh build system did handle this properly.

[01:08:24]This one could recompile dependencies for the correct um target technically not super difficult to do, but we're not doing it right now. So reducted like that.

[01:08:47]Then compile this for reducted.

[01:08:55]Is that enough to get it to run properly? I'm actually not sure. Let's find out.

[01:09:02]Okay. Uh could not find lib shared.

[01:09:04]Okay, that's true.

[01:09:05]because I am not compiling for cross h kind of text editor you making uh it's somewhat inspired by Emacs. Okay, I'm using the wrong uh compiler here. I'm using GCC.

[01:09:30]You should be using uh Arch 64 GCC.

[01:09:38]So, did I just never set that up?

[01:09:41]There's a lot of stuff in this new build system that I haven't needed, so I haven't done it.

[01:09:48]The compiler is this one.

[01:09:53]Resolve compiler for the current environment.

[01:10:10]It looks to me like it should be working.

[01:10:22]Um, it looks to me like this should resolve to arch non-self.

[01:10:46]if I did everything right. I'm just trying to think of it. Uh, okay. Again, resolve compiler gets called by make command. Make command gets called by that is the compilation.

[01:11:19]Hold on. Okay, these two did get recompiled, right? Did you compile them for GCC as well?

[01:11:25]So, this uh this is not working.

[01:11:33]I do have to say when I wrote this thing, I wasn't super sure what I was doing when it came to lisp.

[01:11:40]So, a lot of it doesn't make a whole lot of sense anyway.

[01:11:48]Um, and back to this. This is compile commands. No make command.

[01:12:05]You should be resolving the compiler.

[01:12:11]which should be making it into Wait, what about this current environment?

[01:12:23]Oh.

[01:12:26]Oh, what the [ __ ] is a current environment, man? This is a variable that I'm only using for this. Obviously, that's not going to change.

[01:12:36]It's my dro. Uh, I'm using Red Star OS with KD.

[01:12:44]The important part there is KD.

[01:12:48]Now I see I see the problem. This current environment thing makes no sense. What the [ __ ] was that? It was supposed to be the target, which I believe is mod target. That's what I'm supposed to be using.

[01:13:03]Red mod. Target mod.

[01:13:16]Okay. I almost want to say that looks better.

[01:13:21]Yeah, it does look better because Well, Uno did not get recompiled into the correct um system that it was supposed to.

[01:13:45]How to become a good programmer, mathematician. I don't know about mathematician. I'm going to be honest with you. I'm not good at that [ __ ] Um, but programmer programming pretty much that's how you do it. That's really the only way to do it.

[01:14:05]I don't think reading books is kind of I mean it can teach you the theory. It can probably make you a lot more like give you a lot more formal knowledge, but how do you get good at programming?

[01:14:15]Programming. That's the only way. Again, advice that doesn't uh apply to surgeons, but it applies to us.

[01:14:28]Oh, wait. Hold on.

[01:14:36]No, wait, wait, wait.

[01:14:44]Okay. Which one of you is complaining?

[01:14:46]You're doing beyond. You're doing uno and you're recompiling them for reducted.

[01:15:05]So, aren't you? No, you're not.

[01:15:17]Wait. No. Why not?

[01:15:27]This is doing the exact same thing that the other one is doing.

[01:15:34]It's literally the same thing. So, what's happening?

[01:15:59]Target is this one.

[01:16:15]Name Uno. type den lib I get that but somehow it's still compiling for GCC even though the target is this one and it points to the same build command so once I modified it once it should know what to use right you're using a quick build as Oh, quick build which is calling compile module if it's a library. Oh, okay. The lib compile. Okay. Yeah, libraries are not covered by the thing that I just did.

[01:17:13]So my bad.

[01:17:34]No, I looked in the wrong place.

[01:17:38]All right, lib compile. Here it is.

[01:17:42]takes the libraries maps.

[01:17:53]This lib command list this command here is not updated which means lib command which is called here need to pass in the module as well. So I can include it here and do resolve compiler um red mod target mod and then here the compiler which is a bit of a silly variable now.

[01:18:44]It should always be GCC.

[01:18:48]But in this case, it's not going to be the same cuz here it's actually an assem well, not an assembler, a a library assembler thing. I don't know what that's called.

[01:19:06]Anyway, when you call this function and when you call this function, you pass the mod. So I'm just propagating this value downwards so that it can be used to resolve the com the correct compiler and correct assembler and then you call them both with the module that didn't work. invalid number of arguments two, right? Because the same thing is happening here.

[01:19:41]Pass that in and pass that in.

[01:19:50]Okay.

[01:19:52]All right. So, now it's using GCC. Okay, that's good.

[01:19:58]Ooh.

[01:20:01]undefined reference to write SBK. Well, those are not symbols that you should be referencing at all. All right, this is the final compilation command. It's uh GCC with STDC99 uh Uno Beyond Homebrew include homebrew which is supposed to only be used on Mac is somehow making an appearance here for redacted. Hello Marcy.

[01:20:34]So that's not super correct.

[01:20:38]Oh god. Um, besides that, let me see if there's any other errors. The two libraries, this one that shouldn't be here, the current uh directory, red lib, then compile brain. C3 layout file source shell source against the UNO library, the imaginal library, homebrew, which shouldn't be here, and lib shared producing brain.f.

[01:21:03]Okay, so the rest is good. The only part that's not good is that um somehow uh homebrew made its way here.

[01:21:17]Um [laughter] so I have default dependencies, right? Uh, which I'm pretty sure should have just been if uh type is equal to no not type um tar is equal to Mac.

[01:22:05]I believe that's what I called it. Mac.

[01:22:08]Yeah, cuz homebrew is only used by Mac. But somehow this condition was if true equal true. I must have been testing something and I just never moved it.

[01:22:24]But it still has references to stuff that I shouldn't have. Uh, nonelfgcc stdc9.

[01:22:31]Oh, wait. Um, [ __ ] There is another compilation flag that's missing and I should tell it freestanding and no std lib something like that. F freestanding.

[01:22:52]I need these two compilation flags that are missing.

[01:22:56]uh which are only added if something is compiled for reducted OS [snorts] because it uses its own library.

[01:23:21]Um so essentially if mod uh no red mod target of the module is equal to reducted then you also need to include this and this compilation flex.

[01:23:57]And now they fail.

[01:24:06]Oh, well, this is not a condition. This is an if.

[01:24:11]I need to explicitly tell it to compare them.

[01:24:15]Still not right. Still not right.

[01:24:19]Defund make command. Targeted.

[01:24:26]Oh, supposed to go here.

[01:24:33]All right.

[01:25:04]I understand what's happening. I'm just trying to figure out who's printing this word expected. Expecting.

[01:25:16]Is that a print of mine? That's not mine. Who's printing that? What does that mean?

[01:25:23]Now the thing that is happening here I believe is that the elf file got compiled and I'm trying to run it in the incorrect manner instead of copying over to the system and running it like that. I am trying to run it um directly.

[01:25:47]So that isn't correct but I would love to know what it means. Syntax error word unexpected expecting closing parenthesis.

[01:25:57]Like what do you think this is? This is what happens when you run.

[01:26:04]No, it isn't.

[01:26:09]Uh actually, what does it mean?

[01:26:13]This is even worse cuz I thought, okay, it's somehow executing the program even though it shouldn't because it's a different format entirely. So it's not capable of executing this program and somehow producing this error. But no, it is producing this error. I have no idea who's producing this error.

[01:26:34]I understand exactly what's happening. I what I don't understand is where this error is coming from cuz that's not the correct error.

[01:26:43]This is the error that I was expecting.

[01:26:44]Exc error. But what do you mean syntax error word unexpect? Who? Who's who's saying that? [clears throat] Whose print is this?

[01:27:26]That's an error reported by the almqu quest shell or its derivatives like dash happens to be the default implementation of bin sh used by Ubuntu. probably also Debbian when a word is found while parsing the syntax of a script where a parenthesis is expected instead.

[01:27:51]I how did this happen?

[01:28:00]The weird thing about this is that the it should have never attempted to run this uh program, not run it and encountered a weird error. It should have just said exact format error like it did here, but somehow it did this instead. And that's really, really weird.

[01:28:21]Also, it downloaded a picture of the JavaScript creator there. Oh, and there's Terry Davis.

[01:28:28]Um, anyway, this part I'm going to do manual. I can't I I don't understand what that was, but this part I'm going to do manually, right? Cuz to be honest, I never Well, I did finish the packager for my uh for my system. I just am not using it right now. So, we're going to do it manually.

[01:28:59]We're going to go in here and delete this and uh paste.

[01:29:08]Then, we're going to go into the operating system.

[01:29:12]This better run cuz it's it's taking a long time to to set it up.

[01:29:19]It did not run. Beautiful. Beautiful.

[01:29:22]Beautiful. Beautiful. Uh, it crashed at mouseinput.h25.

[01:29:27]Null pointer accessed.

[01:29:32]Um, all right. So, the code editor is not running on um it is not running on the system right now.

[01:29:53]I do wonder why.

[01:29:55]Now it did give me an error about not being able to find a symbol start. That is actually okay because I don't use start in my system. I go directly to main. So I don't think there should be a silent function that the programmer doesn't know about. That doesn't make any sense.

[01:30:16]Um so all the setup that start does the loader does and I go directly to main.

[01:30:23]So the main fun the main entry point of your program is actually main not start.

[01:30:31]Uh so that not that is not the error but yeah uh this does not run. Um let's not waste any more time on this.

[01:30:49]Yeah, actually do that and that.

[01:30:54]I'll figure this out properly. I'll add the missing parts to the build system so I don't have to manually do all of this every single time. That's really annoying.

[01:31:05]But anyway, um we do have what is definitely a terminal and not a text editor and scripting for it.

[01:31:28]Now, do I maybe want to try running an actual script like this one, for example? Uh, I don't want to have to type this whole thing out manually, and I don't have copy and paste in the editor yet.

[01:31:46]So, how about I just manually put it in here?

[01:31:55]Uh, command buffer. Buffer. Okay.

[01:32:00]buffer right into the command buffer buff this thing. Going to need to escape it a little bit most likely.

[01:32:18]There we go.

[01:32:24]So, that is already pre-loaded into the command buffer. And how do I even know if it worked?

[01:32:56]Oh, it eventually worked. But it says no atomic expression in sub expression.

[01:33:03]Uh, so that's not good.

[01:33:09][snorts] First off, does this even compile anymore?

[01:33:15]like does it still uh work properly?

[01:33:18]Yeah. Final result five. So here it runs. There it doesn't.

[01:33:24]Um even though it's the exact same code, unless it is somehow also including the escapes that I put in.

[01:33:44]Let me just not use those.

[01:33:55]That's the only thing I can think of for this happening. But it's a bit ridiculous. But all right, let's compile it into a library.

[01:34:07]No, it's not.

[01:34:13]You need to compile as a library buddy.

[01:34:20]Oh, that is not the correct. Okay, that is compiling as a library.

[01:34:25]And now, no, somehow when I run it from here, it fails. And also it um sometimes when I press enter doesn't actually enter doesn't actually like try to evaluate the expression. Uh no atomic expression in sub expression.

[01:35:05]It's evaluating something wrong. I just don't understand what it is.

[01:35:10]because this is the code.

[01:35:14]All right, let me try try and do something manually then not do this stuff and instead try to do let's see a simple add one two start with that maybe recompiling cuz that does not ignore what I told it to do.

[01:35:38]This is a really annoying bug. Uh, I don't know how many times I have to press enter before it actually enters.

[01:35:47]Bro, run the command.

[01:35:53]That is a really annoying bug. I'm going to have to fix it for tomorrow.

[01:36:00]It makes this whole thing actually unusable.

[01:36:04]Bro, it doesn't feel like working.

[01:36:24]You know what really sucks is a bug that happens occasionally and then starts happening very often cuz you've been ignoring it and now you can't ignore it anymore.

[01:36:44]It straight up ignores me though.

[01:37:03]It's very annoying.

[01:37:07]All right. What happens if I don't do this? Cuz like we were fine before I started doing this kind of No, it's that's the second time this has happened. Two days in a row.

[01:37:30]Everything's working fine. I don't change a specific part of the code. It refuses to work anymore.

[01:37:40]And yesterday, like I fixed it, but I still don't understand what the actual problem was. So today, um, it's not looking good.

[01:37:52]All right, one last time.

[01:37:56]No, seriously. What the [ __ ] Now it works.

[01:38:08]Okay, it's a different issue.

[01:38:16]Expected string found closing.

[01:38:23]Oh, I'm doing something wrong here.

[01:38:27]I am doing something way wrong.

[01:38:38]because now it works. The second time it doesn't work.

[01:38:45]All right. Let's say that that's debugging that I can do tomorrow and um just move away from this. All right. are using I. What is I?

[01:39:00]Um, all right. So, we should be good kind of. I mean, I did what I wanted to do. I have scripting in the ter in the well, yeah, in the terminal is uh in the shell inside the text editor, which is acting like a terminal.

[01:39:18]Um, but it works.

[01:39:20]So, I'm going to call it successful.

[01:39:25]Um, I need to fix first off. I I need to uh keep working on my build system to uh be able to package applications. That that one's on me and be able to rebuild dependencies with the correct uh architecture.

[01:39:49]Um, and then I need to figure out once I have that and I can rebuild the system the rebuild the terminal easily and put it in the operating system. Figure out why it crashes there. I'll only do that once I actually like have an easy way to put it there. Cuz if I have to manually copy it and paste it, that's not going to be good.

[01:40:12]Um, it's just a little bit of boiler plate I need to write. It's not going to be something particularly complicated.

[01:40:19]Um, and then it's going to be working. We have a terminal. We're able to run commands scripting, which by the way, the language is uh right now it's lisp 1.5.

[01:40:40][ __ ] dusty ass ass language.

[01:40:44]uh with written in with support of the US Army, Navy, Air Force.

[01:40:53]That's how old it is that computing was pretty much a military and sometimes university type of thing. Well, no, at this point it was very much university type of thing. uh sometimes uh US government, but that's how old this version of Lisp is. Um so hoping I have those bugs fixed by tomorrow and I can actually have it in the uh OS, but it's not necessary.

[01:41:23]Most importantly, I'm able to like write stuff properly because again, very annoying that this is not being evaluated.

[01:41:34]But this is also not being evaluated anymore. Okay, [ __ ] off.

[01:41:40]Um, then tomorrow I should be able to uh start designing a dialect of lisp based off of this thing. And then like I said, I should also optimize the interpreter for it because symbol lookup with a linked list. It's a very lispy way of doing things, but it's not very optimized. So, it's going to make it very slow.

[01:42:10]A lot of other things that I'm doing in the list way I could do in other ways with a lot of optimization, skipping a lot of recursion, skipping a lot of that type of stuff.

[01:42:23]Um, but that's not really something super exciting. That's just uh optimization and refactoring. That's uh frankly not a top priority right now in the terms of things that I am refactoring and optimizing.

[01:42:39]We have the operating system.

[01:42:42]We have the text editor and then we have the interpreter. But it works. I can script with it. I can script in lisp.

[01:42:52]And so tomorrow I want to work on the text editing part of this thing and on the lisp language design. So it's still the same thing. Still working on the scripting for the system but actually designing the language a little bit more.

[01:43:08]Designing is a relative term because it's still lisp.

[01:43:13]But yeah, by the way, when I was showing like the genius of lisp and how amazing it is, one thing I completely neglected to mention is how easy it is to parse.

[01:43:25]Lisp is incredibly easy to parse. These are all the rules that I have for parsing lisp. And most of them are just because of the way that my parser is designed. You need to like chain expressions like these. But essentially you just have an s expression which is parenthesis followed by something something something any level of somethings any amount of somethings or an atom which by the way I called list file this part I will change its name to just atom which can be an identifier a string or a number also my tokenizer needs a lot of work uh maybe I'll start looking into that tomorrow as which technically means I need to do a um text processing language.

[01:44:17]But yeah, all of that is part of the unifying again the standardized interfaces like I said that my operating system has. Everything is a file that my code editor has.

[01:44:33]Everything is text I guess we can call it and that list path of everything is a linked list.

[01:44:41]Those three standardized interfaces require very little glue to make them work together uh to make them interact with each other and that means that should make the scripting pretty powerful for the system.

[01:44:56]All right. So tomorrow I'm going to be designing that stuff uh today and tomorrow whenever I have time I'm going to try to make this thing a little bit more stable and maybe even get it running in the operating system.

[01:45:10]All right. Uh that's going to be it for today. Tomorrow I'm stream Am I streaming at the same time tomorrow?

[01:45:15]Depends on weather. Although I think I am.

[01:45:23]Damn. Uh, tomorrow's maximum is last week's minimum. So, yes, I am streaming at 3 p.m. tomorrow. Damn, that's amazing. All right, so I'll be back tomorrow with more lisp stream uh lisp.

[01:45:41]Um, we have Emacs at home and we have plan 9 at home development.

[01:45:48]I'll see you then.

[01:45:56]>> [music]