[Bug] Failed to execute '%userprofile%/.glzr/zebar/start.bat'. Error: Program path is not valid for command

[Graybooked]

Describe the bug

Non-fatal error window appears containing following:

Failed to execute '%userprofile%/.glzr/zebar/start.bat'. Error: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'.

Occurs on fresh install of current latest version of GlazeVM, after having unchecked the allegedly optional zebar installation option.

I am on the latest version of Windows 11 as of writing and a first time user of this program. I predict replicability if you don't check that option on a fresh install on latest W11.

Reproduction

Occurs on fresh install of current latest version of GlazeVM, after having unchecked the allegedly optional zebar installation option.

I am on the latest version of Windows 11 as of writing and a first time user of this program. I predict replicability if you don't check that option on a fresh install on latest W11.

Stack trace or error logs (if applicable)

''' [2m2024-09-01T03:51:40.741710Z[0m [31mERROR[0m [2mglazewm::common::commands::shell_exec[0m[2m:[0m [3merr_message[0m[2m=[0m"Failed to execute '%userprofile%/.glzr/zebar/start.bat'.\n\nError: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'." [2m2024-09-01T03:52:09.161135Z[0m [31mERROR[0m [2mglazewm::common::commands::shell_exec[0m[2m:[0m [3merr_message[0m[2m=[0m"Failed to execute '%userprofile%/.glzr/zebar/start.bat'.\n\nError: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'." '''

Version number

Latest

[Graybooked]

Culprit found, bug is NOT FIXED and will likely appear on first launch for any user who did not choose to optionally install zebar, but bug is REASONABLY USER-CIRCUMNAVIGABLE by simply going into the settings file config.yaml and commenting out the first argument after general by adding a # before startup_commands like so:

# startup_commands: ['shell-exec %userprofile%/.glzr/zebar/start.bat']

[lars-berger]

The default config starts Zebar via startup_commands (has since been updated to shell-exec zebar since v2+ of Zebar).

Reckon the best way to improve this would be to add a new flag (could be named --silence-errors) that hides the error dialog in case a shell-exec command fails. We could then change the default startup command to shell-exec --silence-errors zebar.

The error is currently non-fatal by the way, so it's essentially just a warning. You can press "Ok" in the dialog and the WM will start up normally. I agree that this behavior still isn't ideal though.

[Keshav-writes-code]

its leaving unncessary top margin where zebar would have resided. but not, i dont want that much top margin

[Jy-EggRoll]

In fact, this tool can run entirely without relying on Zebra. I use Windows' built-in taskbar and it works well for me. Therefore, bundling Zebra on first launch is completely unnecessary, in my opinion.

Relatedly, the top margin could also be reduced (as the default setting for users who don't install Zebra). I've noticed this is actually a simple issue that can be resolved by modifying the default yaml configuration file. I could add and reorganize comments in the relevant sections, allowing users to choose freely when editing the yaml file.

I also noticed this is a "good first issue," and as a GitHub newcomer, I'd be happy to hone my skills by tackling this problem.