2023-05-10 07:51:45 <KipIngram   > Ok, got a simple line editor working.  First time in a while I've actually been in a position to actually use a system for serious things.
2023-05-10 07:53:07 <KipIngram   > It's quite simple.  sh will print out my block, with numbered lines.  It puts a > mark on the line number that's the edit target, and I can move that around.  ed edits that line, using the guts of EXPECT that I already had.
2023-05-10 07:54:28 <KipIngram   > Got a word to insert a new line, and will add some to delete a line, copy, paste, and so on.
2023-05-10 08:00:19 <KipIngram   > Hey, what's a nice character to serve as an "end of file" marker?
2023-05-10 08:00:27 <KipIngram   > Visually, I mean?
2023-05-10 08:07:30 <vms14       > 0 1 1000000 range [ 1 2 3 drop drop drop + ] do.list .  this takes 32 seconds XD
2023-05-10 08:07:40 <vms14       > 32.90 real
2023-05-10 08:08:20 <vms14       > but 0 1 1000000 range [ 1 2 3 drop drop drop + ] compile do.list . takes 4 seconds instead
2023-05-10 08:08:37 <KipIngram   > Nice.
2023-05-10 08:08:43 <vms14       > weird actually
2023-05-10 08:08:49 <vms14       > how the heck takes 32 seconds xD
2023-05-10 08:09:25 <vms14       > it is just cause I add words on that "list as code"
2023-05-10 08:10:10 <vms14       > https://termbin.com/othu
2023-05-10 08:10:35 <vms14       > you can test it with:  time perl this.file
2023-05-10 08:10:44 <vms14       > it takes 4 seconds on my machine
2023-05-10 08:11:06 <vms14       > if you go to the last line and remove the 'compile' word on that string it takes 32
2023-05-10 08:11:47 <vms14       > can also change that last line for "repl;" and you have a repl instead xd
2023-05-10 08:11:48 <KipIngram   > It probably isn't weird - it probably makes total sense.
2023-05-10 08:11:55 <KipIngram   > I don't know how your system actually works, though.
2023-05-10 08:12:01 <vms14       > yeah, it's a lot of iterations after all
2023-05-10 08:12:17 <vms14       > it's just the interpreter is slow, but didn't expect this difference
2023-05-10 08:13:49 <vms14       > I can "compile" whole packages, but "code as lists" won't be compiled
2023-05-10 08:14:15 <vms14       > if the "compiler" finds a list returns a closure that pushes that list
2023-05-10 08:14:28 <vms14       > xD
2023-05-10 08:14:54 <vms14       > you have to add "compile" to the code-lists to get them compiled
2023-05-10 08:15:47 <vms14       > or the name of a word, or a number
2023-05-10 09:20:07 <veltas      > drive-by profiling
2023-05-10 09:20:58 <veltas      > KipIngram: That sounds nice, as for EOF marker it really depends
2023-05-10 09:21:16 <veltas      > If blocks then maybe put something like | at the end of every single line
2023-05-10 09:21:58 <veltas      > If it's a file or file-with-line-endings-stuffed-into-a-block then end with one $ character maybe or something
2023-05-10 10:10:16 <drakonis    > i'm finally starting to figure out how to operate the assembler i chose
2023-05-10 10:10:27 <drakonis    > fasmg is a hoot
2023-05-10 12:00:25 <KipIngram   > Well, there's a newline at the end of lines - it's  obvious where those are.
2023-05-10 12:00:36 <KipIngram   > For the moment I'm going with ∘
2023-05-10 12:00:45 <KipIngram   > Just to indicate that there is a null byte there.
2023-05-10 12:00:55 <KipIngram   > Which is important - it has to remain in the block.
2023-05-10 12:01:01 <thrig       > fasting o
2023-05-10 12:01:26 <KipIngram   > Lines that I edit need to have a newline at the end, so I don't want to try to edit the line that shows ∘
2023-05-10 12:01:51 <KipIngram   > I can "go to" that line, but I need to ii first to move the rest of the block up a byte and insert a newline there.
2023-05-10 12:01:55 <KipIngram   > Then I can edit it.
2023-05-10 12:02:10 <KipIngram   > I could build in a check for that of course, but I haven't yet.
2023-05-10 12:10:07 <veltas      > I've been emailed by a recruiter but the contents seems to be some sort of phishing link
2023-05-10 12:10:32 <veltas      > It contains what look like pretty convincing internal emails from some internal company thread
2023-05-10 12:11:16 <veltas      > I replied to their email (which was a real email) telling them to notify their IT dept, looks like their laptop's compromised or something
2023-05-10 12:11:37 <thrig       > maybe it's for a red team security position
2023-05-10 12:11:47 <veltas      > lol maybe
2023-05-10 12:12:51 <thrig       > xkcd://125
2023-05-10 12:13:15 <unjust      > veltas: did you check the headers?
2023-05-10 12:13:45 <veltas      > No I can't figure out how on my webmail, but I'm pretty sure it contains a real internal thread from that recruiter's inbox
2023-05-10 12:14:15 <unjust      > some of these spammy social-engineer-your-employees-before-bad-guys-do companies add a header like X-PHISHTEST with a splurb about the campaign they were commissioned to run
2023-05-10 12:14:27 <veltas      > You can just tell, the stuff they are discussing is relevant to their work, requires insider knowledge to fabricate, and also the content is totally irrelevent to the phising attempt at top
2023-05-10 12:15:20 <veltas      > It's just added as a quote as if they're replying to some larger conversation, I'm pretty sure a virus has just pulled it out of their inbox at random and attached a phising message at top
2023-05-10 12:15:52 <KipIngram   > Sounds right.
2023-05-10 12:15:59 <veltas      > The email went to my personal email address, not company
2023-05-10 12:16:29 <veltas      > And I've contacted this recruiter a loooong time ago, so I'm probably in a contacts file somewhere internally to them
2023-05-10 12:18:46 <veltas      > Anyway I've emailed them back so hopefully they see that and "tell IT" (i.e. ask IT for a rebuild without saying why and stop visiting torrent websites at work)
2023-05-10 14:10:24 <gordonjcp   > 17:11 < thrig> maybe it's for a red team security position
2023-05-10 14:10:38 <gordonjcp   > thrig: "have your CV on my desktop before 4pm and you're hired"?
2023-05-10 14:17:59 <KipIngram   > Heh.  My most fun "hire" was when I hired a very well-respected analog guy away from the company we'd worked together at.  I did it with two phone calls - called him and asked him if he'd come work for us, and then called the HR manager and gave her the details and asked her to get him an offer letter by the end of the day.
2023-05-10 14:18:41 <KipIngram   > There was really nasty politics at that company, and when I first got there they had a consultant doing their analog work, and he was firmly on the "other political team."
2023-05-10 14:19:00 <KipIngram   > And I don't know analog well enough to have been able to challenge him on things.
2023-05-10 14:19:25 <KipIngram   > So I just hired this guy and announced that he'd have final say over everything analog.
2023-05-10 14:19:32 <KipIngram   > The consultant quit two weeks later.
2023-05-10 14:20:09 <KipIngram   > The guy that was my primary "opponent" in all of that was totally pissed over it, but he couldn't criticize it because the guy I hired was too well known in the industry.
2023-05-10 14:20:24 <KipIngram   > No one could argue that he wasn't a good acquisition.
2023-05-10 14:21:03 <KipIngram   > But I wanted that whole thing done and committed before anyone had a chance to try to argue against it.
2023-05-10 14:21:42 <KipIngram   > It was completely obvious after the fact what I'd accomplished strategically with that move.
2023-05-10 17:22:30 <KipIngram   > Managed to get that editor into my blk.dat file.  I can past blocks of text into the interpreter, but it's a line editor, so it can only take it one line at a time.
2023-05-10 17:22:51 <KipIngram   > I tried doing a big full-block EXPECT, but the newlines don't get handled right.
2023-05-10 17:22:59 <KipIngram   > So I had to paste it a line at the time.
2023-05-10 17:23:17 <KipIngram   > That's a disadvantage compared to the screen editor I wrote last time.
2023-05-10 17:23:28 <KipIngram   > But it was a good bit bigger and more complex.
2023-05-10 17:23:49 <KipIngram   > This is 21 lines and 682 bytes.
2023-05-10 17:24:01 <thrig       > bloat
2023-05-10 17:24:30 <KipIngram   > :-)
2023-05-10 17:55:19 <veltas      > I've said before on here that I broke Misra's website accidentally
2023-05-10 17:55:21 <veltas      > For like a month
2023-05-10 17:56:31 <veltas      > Or I'm not sure I owned up to it outside of a few people but basically I set my password to something 256 characters long because they said that was the max, and my password manager made that easy to do
2023-05-10 17:56:46 <veltas      > I guess in hindsight that was pointless
2023-05-10 17:57:11 <veltas      > But the second I did that the whole website stopped working for about a month, so I suspect I broke it, an old PHP thing
2023-05-10 17:57:22 <veltas      > And eventually it came back brand new
2023-05-10 17:57:41 <veltas      > I don't think anyone there knew how to fix it, original PHP devs long gone
2023-05-10 17:58:08 <veltas      > I just have that magic touch of death when it comes to tech
2023-05-10 18:00:15 <KipIngram   > One of my daughters managed to delete the whole Wikipedia article on Apollo 13 once when she was first starting out in computers.
2023-05-10 18:01:18 <KipIngram   > You must be a wizard!
2023-05-10 18:01:51 <KipIngram   > That book series I enjoy - that's a thing.  Wizards and technology don't mix.  And if he TRIES to hex down some electronic system, it's as good as dead.
2023-05-10 18:02:01 <KipIngram   > "Hexus!"
2023-05-10 18:03:17 <KipIngram   > He won't even carry a semiautomatic handgun; revolver's less likely to jam on him.  So it's not just electornics.
2023-05-10 18:03:17 <veltas      > Off by one errors on MISRA's backend, good job
2023-05-10 18:03:58 <veltas      > And a sundial instead of a clock?
2023-05-10 18:04:40 <KipIngram   > No, the writer missed that one.  But he does use candles because light bulbs blow too frequenty, and he uses a real "icebox."
2023-05-10 18:04:57 <KipIngram   > And has a fireplace rather than gas or electric heat.
2023-05-10 18:05:19 <KipIngram   > One thing this very effectively accomplishes is to prevent the series from being full of him finding stuff online.
2023-05-10 18:05:30 <KipIngram   > No phone, no computer, etc.
2023-05-10 18:05:56 <KipIngram   > His "person" at the police office won't let him into her office until she's turned off her computer.
2023-05-10 18:06:21 <veltas      > I need to stop talking about MISRA, I'm worried they're going to sue me
2023-05-10 18:06:31 <KipIngram   > How long ago was this?
2023-05-10 18:06:41 <veltas      > Like a year ago
2023-05-10 18:07:23 <KipIngram   > But if it was before they announced a max password length you technically didn't "do" anything wrong.
2023-05-10 18:08:01 <veltas      > The law regarding misuse of computers is open enough to interepretation to cause me trouble
2023-05-10 18:08:34 <veltas      > Anyway, changing the subject
2023-05-10 18:08:47 <veltas      > Let's see if I can get ilo-amd64 finished tonight