Documentation

A shared global variable for the OutputHandle.

Holds a lock while performing an action. This allows the action to perform its own output to the console, without using functions from this module.

While this is running, other threads that try to lockOutput will block. Any calls to outputConcurrent and createProcessConcurrent will not block, but the output will be buffered and displayed only once the action is done.

Blocks until we have the output lock.

Tries to take the output lock, without blocking.

Only safe to call after taking the output lock.

Use this around any actions that use outputConcurrent or createProcessConcurrent

This is necessary to ensure that buffered concurrent output actually gets displayed before the program exits.

Blocks until any processes started by createProcessConcurrent have finished, and any buffered output is displayed. Also blocks while lockOutput is is use.

withConcurrentOutput calls this at the end, so you do not normally need to use this.

Values that can be output.

Displays a value to stdout.

No newline is appended to the value, so if you want a newline, be sure to include it yourself.

Uses locking to ensure that the whole output occurs atomically even when other threads are concurrently generating output.

When something else is writing to the console at the same time, this does not block. It buffers the value, so it will be displayed once the other writer is done.

Like outputConcurrent, but displays to stderr.

(Does not throw an exception.)

Use this to wait for processes started with createProcessConcurrent and createProcessForeground, and get their exit status.

Note that such processes are actually automatically waited for internally, so not calling this explicitly will not result in zombie processes. This behavior differs from waitForProcess

Wrapper around createProcess that prevents multiple processes that are running concurrently from writing to stdout/stderr at the same time.

If the process does not output to stdout or stderr, it's run by createProcess entirely as usual. Only processes that can generate output are handled specially:

A process is allowed to write to stdout and stderr in the usual way, assuming it can successfully take the output lock.

When the output lock is held (ie, by another concurrent process, or because outputConcurrent is being called at the same time), the process is instead run with its stdout and stderr redirected to a buffer. The buffered output will be displayed as soon as the output lock becomes free.

Currently only available on Unix systems, not Windows.

Wrapper around createProcess that makes sure a process is run in the foreground, with direct access to stdout and stderr. Useful when eg, running an interactive process.

Buffered output.

Adds a value to the output buffer for later display.

Note that buffering large quantities of data this way will keep it resident in memory until it can be displayed. While outputConcurrent uses temp files if the buffer gets too big, this STM function cannot do so.

A STM action that waits for some buffered output to become available, and returns it.

The function can select a subset of output when only some is desired; the fst part is returned and the snd is left in the buffer.

This will prevent it from being displayed in the usual way, so you'll need to use emitOutputBuffer to display it yourself.

Use with outputBufferWaiterSTM to make it only return buffered output that ends with a newline. Anything buffered without a newline is left in the buffer.

Emits the content of the OutputBuffer to the Handle

If you use this, you should use lockOutput to ensure you're the only thread writing to the console.