Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support for callbacks after a task is complete?

Open
  • Is something wrong?
#72 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
vim
Domain
developer-experience

Research direction

Start with the linked notify example in the wiki and inspect the existing notify=echo task behavior. Define how a callback notification should receive task completion and exit-status information, then verify that the callback is invoked for successful, failed, and still-running task states.

Written by the indexing model from the issue text.

Description

Hey,

This is a really neat plugin, and I already have defined a bunch of tasks. One feature I haven't found yet and that I miss is the ability to have a (vimscript) callback on exit. In particular, I want to update my statusline (e.g. have a red square) if the exit code is >= 1 , green square if the exit code is 0 and a yellow square if the task is still running.

  1. Is it possible to do something like that already?
  2. If not, would you consider adding a callback feature that would enable me to do this?

Edit: Looks like the notify example is a nice starting point if I just want the message to be echoed on the statusline. In that case, I'll add notify=echo to the task. It would be nice to also have notify=callback:my_vimscript_function that I could call.

Dominant language
Vim Script
Stars
936
Forks
32
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skywind3000/asynctasks.vim

All issues in skywind3000/asynctasks.vim

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.