atagen
atagen
Seems to be working rather smoothly so far, great stuff. I'm not sure if I'm misunderstanding or misusing the process lookup, though - `bg { sleep 1000 }; fg sl`...
Okay, so looking closer at the jobs, the process name is always set to `exec`. From what you said about command/params, it should use the full argc+argv for the process...
Yes, the semicolon was shorthand, sorry - the process is definitely alive but only "exec" or some part thereof can be used as a string to foreground it. No other...
> ## Flags > This admittedly isn't all that ergonomic for frequently used functions Yes, I wouldn't really want to use flags outside of an executable, especially for short everyday...
Okay, the more I think about it the more I prefer the idea of allowing functions with the same name but different arities - it fully and explicitly encodes the...
> Another option is to abuse the default value. You code already appears to do this actually Sadly ineffective, as 1. it still asks for a value, and 2. `[]`...
Sounds perfect - compact and logical. And thanks for working through this so patiently :)
Understandable change - so I should stick with `if { $var }` to check for set-ness? Does this make a !bool being false and unset equivalent? Not really a problem...
I'm not sure if I've done something wrong here: ``` ❯ murex --version murex v6.4.0309 (develop) GPL v2 2018-2024 Laurence Morgan ❯ function test (t: str) { echo $t }...