Module errors

Error context system based on a thread-local representation of the call stack, itself based on the instructions that are sent between threads.

Help wanted

There is an ongoing endeavor to improve the state of error handling in zellij. Currently, many functions rely on [unwrap]ing Results rather than returning and hence propagating potential errors. If you’re interested in helping to add error handling to zellij, don’t hesitate to get in touch with us. Additional information can be found in the docs about error handling.

Modules

prelude

Re-exports of common error-handling code.

Structs

ErrorContext

A representation of the call stack.

Enums

BackgroundJobContext

ClientContext

Stack call representations corresponding to the different types of [ClientInstruction]s.

ContextType

Different types of calls that form an ErrorContext call stack.

PluginContext

Stack call representations corresponding to the different types of [PluginInstruction]s.

PtyContext

Stack call representations corresponding to the different types of [PtyInstruction]s.

PtyWriteContext

ScreenContext

Stack call representations corresponding to the different types of [ScreenInstruction]s.

ServerContext

Stack call representations corresponding to the different types of [ServerInstruction]s.

ZellijError

Traits

ErrorInstruction

FatalError

Special trait to mark fatal/non-fatal errors.

LoggableError

Helper trait to easily log error types.

ToAnyhow

Helper trait to convert error types that don’t satisfy anyhows trait requirements to anyhow errors.

Functions

get_current_ctx

handle_panic

Custom panic handler/hook. Prints the ErrorContext.