It seems that all error messages, which are returned by a Run() method of a command struct, are prefixed with the call chain of the program.

Consider the following sample program:

package main

import (
	"errors"
	"fmt"
	"github.com/alecthomas/kong"
)

type Context struct {}

type Cmd struct {}

func (c *Cmd) Run(ctx *Context) error {
	return errors.New("Command failed.")
}

var cli struct {
	Cmd Cmd `cmd:"" default:"1"`
}

func main() {
	ctx := kong.Parse(&cli)
	err := ctx.Run(&Context{})
	if err != nil {
		fmt.Println(err)
	}
}

• In kong v0.7.1, this program would print: (https://go.dev/play/p/I154MFjk37_t)
  • Command failed.
• In kong v0.8.0, this program would print: (https://go.dev/play/p/rHI7PEwHCkc)
  • main.Cmd.Run(): Command failed.

In my application, the error messages returned by Run() are end-user facing, so the “call-chain” prefix wouldn’t mean anything to my users and might potentially confuse them.

Would it be possible to drop the prefixing, and just pass on the original error object as is? I.e., without wrapping, modifying, or re-serializing the error object at all?

It seems that the new behaviour was introduced in #344, where callbacks.go now re-serializes the original error message, in order to add the prefix info: