Background Blocks
How Blocks interact with background process output.
Last updated
Was this helpful?
How Blocks interact with background process output.
Last updated
Was this helpful?
Commands can start background processes that continue even after they exit. You can also start a background process directly from the shell, such as by running it with &.
If Warp receives output that is likely from a background process, the output goes into a background block. Background blocks act like regular blocks, except that they don't have an associated command.
This lets you use all of Warp's block features with background output, such as sharing and bookmarking.
Background blocks are automatically created as needed, in between regular blocks running. If you run commands while a background process is still producing output, that output gets split into multiple blocks interleaved with your commands.
There are some limitations, because Warp doesn't know which process any given output came from:
If a background process writes output while a foreground command is running in a regular block, the output goes into that block.
If there are multiple background processes running at the same time, their output may be mixed together.
In addition, if you start entering a command while another one is running (typeahead), in some cases Warp will mistake the partial command for background output. The most common cause is editing typeahead when using bash versions older than 4.0 (for example, deleting and re-typing part of it).