This function performs the equivalent of [method@Gio.
AppInfo.launch_uris], but is intended primarily for operating system components that launch applications. Ordinary applications should use [method@Gio.AppInfo.launch_uris].
If the application is launched via GSpawn, then spawn_flags, user_setup and user_setup_data are
used for the call to [func@GLib.spawn_async]. Additionally, pid_callback (with pid_callback_data) will be called
to inform about the PID of the created process. See [func@GLib.spawn_async_with_pipes] for information on certain parameter conditions
that can enable an optimized [`posix_spawn()`](man:posix_spawn(3)) code path to be used.
If application launching occurs via some other mechanism (for example, D-Bus activation) then spawn_flags, user_setup
, user_setup_data, pid_callback and pid_callback_data are ignored.
| this |
a [class@GioUnix.DesktopAppInfo] |
| uris |
List of URIs |
| launch_context |
a [class@Gio.AppLaunchContext] |
| spawn_flags |
[flags@GLib.SpawnFlags], used for each process |
| user_setup |
a [callback@GLib.SpawnChildSetupFunc], used once for each process. |
| pid_callback |
Callback for child processes |
| pid_callback_data |
User data for |
| user_setup_data |
User data for |
|
`TRUE` on successful launch, `FALSE` otherwise. |