Laurence Morgan

hi @joshahussey I think the issue here isn't that the process isn't running in the background but rather the commands you're running are builtins, which are threads rather than processes...

ahhh yes. I can see the issue. The script finishes before `bg` finishes forking `waybar`. eg ``` » murex -c "bg { sleep 999 }" » ps aux | grep...

@joshahussey An update on this: I've spent the last couple of months prototyping different behaviours but the problem is having consistent behaviour between external executables (like `waybar`) vs builtins and...

@testwill nice catch. I'll merge this into `develop` though, because `master` releases auto-trigger new builds and I'd like to have an attached changelog first

This might help explain some of the design decisions behind the comments (and the confusing messages you saw): The general history of the comments are the following: - `get` /...

To add to the inconsistencies, it works as an expression if you specify that it is a scalar. eg ``` » $1foo = 1 + 2 » $1foo 3 ```...

Nice catch. You're right about `tree.statement` being `nil` Escaping in comments was intended to be used as a way of documenting a command's parameters, eg ``` ls # directory listing...

Funny enough, I'm working through some edge case job control bugs at the moment. Thanks for raising this, it slots nicely into the wider piece I'm working on.

@tiymat I haven't had chance to look at this yet but I have just merged some new job control code into `develop`. So if you have any spare time, can...

I think `.bashrc` is being sourced in both releases. It's more likely it's a break in ``` config set proc force-tty true ``` Bash was always a little more sensitive...