This function performs the equivalent of g_app_info_launch_uris(),
but is intended primarily for operating system components that
launch applications. Ordinary applications should use
g_app_info_launch_uris().
If the application is launched via GSpawn, then spawn_flags, user_setup
and user_setup_data are used for the call to Spawn.async.
Additionally, pid_callback (with pid_callback_data) will be called to
inform about the PID of the created process. See Spawn.asyncWithPipes
for information on certain parameter conditions that can enable an
optimized posix_spawn() codepath to be used.
If application launching occurs via some other mechanism (eg: D-Bus
activation) then spawn_flags, user_setup, user_setup_data,
pid_callback and pid_callback_data are ignored.
This function performs the equivalent of g_app_info_launch_uris(), but is intended primarily for operating system components that launch applications. Ordinary applications should use g_app_info_launch_uris().
If the application is launched via GSpawn, then spawn_flags, user_setup and user_setup_data are used for the call to Spawn.async. Additionally, pid_callback (with pid_callback_data) will be called to inform about the PID of the created process. See Spawn.asyncWithPipes for information on certain parameter conditions that can enable an optimized posix_spawn() codepath to be used.
If application launching occurs via some other mechanism (eg: D-Bus activation) then spawn_flags, user_setup, user_setup_data, pid_callback and pid_callback_data are ignored.