Skip to content

[BUG] Issue: Ghostty configuration errors after ML4W dotfiles update #1503

@SagarOnArch

Description

@SagarOnArch

Describe the bug

class: value required
dotfiles-floating: invalid field

This happens immediately when I trigger the update from Waybar

Possible cause

$(cat ~/.config/ml4w/settings/terminal.sh) --class dotfiles-floating -e ~/.config/ml4w/scripts/ml4w-network

Ghostty seems to interpret this incorrectly in the current configuration, resulting in:

class: value required

dotfiles-floating: invalid field

Ghostty expects:

--class=

or

--class value

But if something in the update writes something like:

class: dotfiles-floating

or injects dotfiles-floating incorrectly into config, Ghostty may parse it as a separate field, which produces:

dotfiles-floating: invalid field

So the parser basically goes:

class: (missing value)
dotfiles-floating: ??? (unknown key)

Which explains the two errors together.

Environment

  • Distro: CachyOS
  • Terminal: Ghostty
  • Dotfiles repo: ML4W dotfiles

Steps to reproduce

  1. Install ML4W dotfiles
  2. Run the ML4W update script
  3. Launch Ghostty
  4. Ghostty shows a configuration error pop-up

Expected behavior

Ghostty should start normally without configuration errors when launched through the ML4W dotfiles setup.

Screenshots

Image

Distribution

Other (please specify below)

If Other, specify

CachyOS

Additional context

replace

--class dotfiles-floating

with

--class=dotfiles-floating

$(cat ~/.config/ml4w/settings/terminal.sh) --class=dotfiles-floating -e ~/.config/ml4w/scripts/ml4w-install-system-updates

By changing it like this issue resolves

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions