Exec a command and exit

[gaultierq]

Hello! Thanks for this awesome library. I’m new to Go and building a CLI with Bubbletea that launches a command and exits.

I’m using syscall.Exec to replace the Go process with the new binary. It works in some cases, but for some commands (like /bin/env) the terminal layout gets messed up. I saw Program.ReleaseTerminal and wondered if that’s the right way to fix it.

[lrstanley]

Take a look at the following examples for executing a command, then eventually returning to the TUI:

• bubbletea v1: https://github.com/charmbracelet/bubbletea/blob/main/examples/exec/main.go
• bubbletea v2: https://github.com/charmbracelet/bubbletea/blob/v2-exp/examples/exec/main.go

With that being said, if the intention is to use bubbletea to invoke another tool, and not returning back to the TUI, you can use Program.ReleaseTerminal (from a goroutine or similar), though it may be better to use the tea.Quit command to exit from the model, so you don't have to do async operations to be able to call Program.ReleaseTerminal. Run() returns the final model, so you could do something like this (syntax may change slightly between v1 and v2):

func (m model) Update(msg tea.Msg) (tea.Model, tea.Cmd) {
	if acquiredNeededExecConfig {
		m.yourExecConfig = [...]
		return m, tea.Quit
	}
}

and in your main or similar:

func main() {
	finalModel, err := tea.NewProgram(initialModel())
	if err != nil {
		panic(err)
	}
	// use finalModel.yourExecConfig to exec the follow-up tool. because tea.Quit was used,
	// the terminal has already been released, and should allow normal operations now.
}

[gaultierq]

Thanks a lot ! I've used tea.Quit and it works well. I had to cast the final Model into my a concrete model but I ended up with what I want. Thanks