The `windows.toast_notification()` function is not working properly. about wezterm HOT 7 OPEN

Same here, window:toast_notification doesn't seem to do anything for me?

from wezterm.

I think this has something to do with the installation method.

On Windows, notifications work when installed with winget (i.e. using the installer as non-portable), while with scoop (as a portable install) not notifications show. I tested this the same way as @leetking, can someone else confirm this?

from wezterm.

I too use scoop and toast notifications do not work. I'll try installing the non portable version and testing.
EDIT: toasts work when using wezterm installed via the setup.exe

from wezterm.

I did some tests as follows:

1. The wezterm installed by scoop actually downloads the non-portable installation package from the release page https://github.com/wez/wezterm/releases/download/20240203-110809-5046fc22/WezTerm-windows-20240203-110809-5046fc22.zip , so after I manually downloaded the portable zip, decompressed it and used it, I found that notification could not be triggered either.
2. After downloading setup.exe and installing it, click on the newly installed wezterm-gui.exe. The experiment found that notification can be triggered.
3. Interestingly, I also opened wezterm-gui.exe installed by scoop and found that nofication can also be triggered.
4. Uninstall the wezterm installed through setup.exe and reopen the wezterm installed by scoop. Nofication cannot be triggered.

Presumption: The setup.exe installation will register some information in the system, but the scoop or downloaded portable version lacks this information, resulting in the failure to trigger the notification.

from wezterm.

1. The wezterm installed by scoop actually downloads the non-portable installation package from the release page ...

Scoop packages usually extract the contents .exe, so the bundled installer is not run. From looking at the manifest, this seems to be the case. Although I do not really know any technical details on what that means.

3. Interestingly, I also opened wezterm-gui.exe installed by scoop and found that nofication can also be triggered.

I can confirm this, probably because the installer does something® that makes the notification possible irrespective of the installation path.

The setup.exe installation will register some information in the system, but the scoop or downloaded portable version lacks this information, resulting in the failure to trigger the notification.

My first guess would be a registry key, scoop does not automatically edit the registry by default.

from wezterm.

https://learn.microsoft.com/en-us/answers/questions/159295/no-desktop-notifications-for-portable-apps-from-ne
According to this article, it seems to be a common problem with portable programs.
According to the answer of Eleven Yu:

The notifications settings can be deployed by GPO or registry.
Group Policy:
Computer Configuration\Administrative Templates\Windows Components\App Privacy - Let Windows apps access notifications
Registry:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\AppPrivacy

I need to register a GPO, but I don’t know much about it.

from wezterm.

According to my understanding: Wezterm's setup.exe is generated by inno setup. After it is installed, it appears as an application on the Windows system. The installed program can be found in Notifications & actions, so you can control whether notifications are allowed to be issued. , but the portable program does not appear as an application to windows.

from wezterm.