Skip to content

fix: prevent MANGOHUD_CONFIG from blocking the user config file - #4569

Open
latin-1 wants to merge 1 commit into
bottlesdevs:mainfrom
latin-1:patch-1
Open

fix: prevent MANGOHUD_CONFIG from blocking the user config file#4569
latin-1 wants to merge 1 commit into
bottlesdevs:mainfrom
latin-1:patch-1

Conversation

@latin-1

@latin-1 latin-1 commented Jul 4, 2026

Copy link
Copy Markdown

Description

Currently, when “Display On Game Start” is disabled, MANGOHUD_CONFIG=no_display is set, which causes the user’s own config file, such as ~/.config/MangoHud/MangoHud.conf, to be ignored.

This usually isn’t the expected behavior, and it’s also inconsistent with what happens when the option is enabled. We should use MANGOHUD_CONFIG=read_cfg,no_display instead.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce.

  • Test A
  • Test B

Currently, when “Display On Game Start” is disabled, `MANGOHUD_CONFIG=no_display` is set, which causes the user’s own config file, such as `~/.config/MangoHud/MangoHud.conf`, to be ignored.

This usually isn’t the expected behavior, and it’s also inconsistent with what happens when the option is enabled. We should use `MANGOHUD_CONFIG=read_cfg,no_display` instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant