Releases: mafredri/zsh-async
Releases · mafredri/zsh-async
v1.8.6
v1.8.5
v1.8.4
1.8.3
1.8.1
1.8.0
Changes
Since 1.7.2
- Only set ZLE watcher after a callback has been registered (317d19e)
- Improve worker startup procedure in async_start_worker (#39) (361dc17)
- Improved error state handling (#37) (32548d3)
Since 1.7.1
- travis: Fix building of zsh 5.0.2 and 5.0.8 (#32) (98d32af)
- Prevent infinite loop in case of broken zpty file descriptor (#31) (43de5e0)
- travis: Switch to using .tar.xz since .tar.gz is unavailable (e6d9372)
Since 1.7.0
1.7.0
Changes
- New: Introduce
async_worker_eval
for updating the worker environment (#29)- For example,
async_worker_eval my_worker cd $PWD
, would change the current working directory inside the worker, which would also be inherited by subsequent jobs - Can be used as an alternative to passing
$PWD
to every async job
- For example,
- Fix: Prefix async job output to prevent external corruption (#28)
- This also fixes some cases of invalid arguments being passed to the callback when the output buffer becomes corrupt
1.6.2
It's been a while since I wrote release notes for zsh-async
, I think it's about time.
Changes from v1.5.2
to v1.6.2
- Avoid creation of implcit global variables
- Add 6th parameter when invoking callback functions, has next, indicates that callback will be invoked again within this event loop
- Replace
async.plugin.zsh
symlink withsource
for better compatibility - Add
ASYNC_VERSION
environment variable - Avoid array quoting on error states in
async_process_results
1.5.1
1.5.0 consequential-canary
Changes
- ZLE watchers are now used on all versions of zsh (the
SIGWINCH
kill signal is no longer needed to notify when a job is complete)- Tested to work on at least zsh versions: 5.0.2, 5.0.8 and 5.1.1
- Small improvements to
async_flush_jobs
(via_killjobs
)
Full changelog: v1.4.0...v1.5.0