fuzzel: add testbed

[0xda157]

Submission Checklist

• I certify that I have the right to submit this contribution under the MIT license
• Commit messages adhere to Stylix commit conventions
• Theming changes adhere to the Stylix style guide
• Changes have been tested locally
• Changes have been tested in testbeds
• Each commit in this PR is suitable for backport to the current stable branch

Notify Maintainers

@MrSom3body

[MrSom3body]

Is it okay to set a keybind for fuzzel? Otherwise, it’s hard to open the launcher again

[trueNAHO]

Is it okay to set a keybind for fuzzel? Otherwise, it’s hard to open the launcher again

Good point. However, since this is the case with nearly all testbeds, it would be better to generally solve this issue by providing a consistent interface for re-running the test code inside the testbed. I suppose this involves installing stylix.testbed.ui.application and stylix.testbed.ui.command.text into the testbed. I will open a PR for this later.

In the meantime, the testbed should be fine.

[stylix-automation]

Successfully created backport PR for release-25.05:

• [release-25.05] fuzzel: add testbed #1791

[trueNAHO]

Is it okay to set a keybind for fuzzel? Otherwise, it’s hard to open the launcher again

Good point. However, since this is the case with nearly all testbeds, it would be better to generally solve this issue by providing a consistent interface for re-running the test code inside the testbed. I suppose this involves installing stylix.testbed.ui.application and stylix.testbed.ui.command.text into the testbed.

This should be resolved by commit 662dd8a ("stylix/testbed/modules/application: allow re-running test code") once it gets merged in #1662.