Interesting. There is this example in the docs:
let result = $ cat file.txt | grep "READY" $ failed {
echo "Failed to read the file"
}
https://docs.amber-lang.com/basic_syntax/commands
How can we know for sure what failed here? Was it the cat or the grep? My instinct says the pipe returns the code of the last cmd or failure, which could be either.
Perhaps it’s just a contrived example and it would be better to separate testing file existence from grepping in real code…
This is new:
https://github.com/dkorecko/PatchPanda
Self-hostable Docker Compose stack update manager.
And
when you choose to update, PatchPanda edits compose/.env files and runs
docker compose pullanddocker compose up -dfor the target stack. You can also view live log.
Discovered in the latest Self Host Weekly:
https://selfh.st/weekly/2025-11-28/
I have not tried it myself tho.
The link seems to say Threads support is only available as an add-on and therefore not simple to use with containerised HASS. This would be true for any Threads antenna though.
That’s good. There are also editors that can run it for you and highlight the issues whilst you type, neovim being one.
$() for me, to quote from
https://www.shellcheck.net/wiki/SC2006
Backtick command substitution
`...`is legacy syntax with several issues.
- It has a series of undefined behaviors related to quoting in POSIX.
- It imposes a custom escaping mode with surprising results.
- It’s exceptionally hard to nest.
$(...)command substitution has none of these problems, and is therefore strongly encouraged.
deleted by creator
Thanks for that, makes sense. I like that Amber gives the ability to code more defensively/robustly where appropriate but can also get out the way if you just need to run a bunch of BASH raw.