@RubenVerg so what I was going for with the funny triangles and dots was a visual metaphor of which side has the drop on
Meaning as long as the dots are kept on the side they're on, it's fine
@RubenVerg honestly if it looked like :> as a single character that'd be good
Because it's intended to be the same as x[1:] but slightly visually different to indicate the behaviour is slightly different
Also, I've had an idea
The glyphs you're making will be the default font on the website
But I might make a variant font where each symbol is represented by what I wish I could draw if Unicode were something I could forcibly add to
So like each glyph would be a better representation than what is available in Unicode
The point being that when you want to edit things in a way that looks like what you'd get in other fonts, use vyxal386 (be great if we called it vyxal420 though)
But if you want an easy mode, use the easy mode font (call it vyxal69)
It'd be good to have both fonts. One for preview of what other people see, and one for beginners
Professionals use the 420 variant, people getting used to things would use the 69 variant. 420 is something you'd put in a museum, 69 is what you'd whip up on a napkin while eating soup at a petrol station diner.
ok what if: instead of making the code to execute a parameter to VyTerminal's imperative handle's start(), I make it a prop and have start() take no parameters
which means I can run code if it isn't empty when VyTerminal mounts
also VyRunner should probably handle timing out itself
while there's on-site search, I still find myself going to the table a lot
anyhow, in terms of codepage formation, I've created a text file to start figuring out which functions still need to be added, and which functions are just overloads
