Lanching Programs

[McPherran]

spawn_async_no_shell(...) is used for actions e.g. keybind Execute and menu items with no command line shell involved?

spawn_async_no_shell(...) also used for autostart and shutdown but in that case spawn_async_no_shell("sh ...") is used for actions?

Generally, I am interested in launching desktop programs directly into labwc without /bin/sh or other shell being used.

In line with this, I'm also interested in ability to launch a program by using a command-line command but again the idea would be that the program launches directly into labwc with no shell involved even though started from a command line in a shell. In this case, I would like the program to be process-owned by labwc and not the command shell that the command line was used in. Something like an "exec" etc. to run the program (e.g. via message to labwc).
E.g: any_shell_prompt> labwc-exec example_program_name ?

Can actions be defined in rc.xml then used directly as actions for keybinds and menu entries?

[tokyo4j]

spawn_async_no_shell(...) is used for actions e.g. keybind Execute and menu items with no command line shell involved?

Yes.

spawn_async_no_shell(...) also used for autostart and shutdown but in that case spawn_async_no_shell("sh ...") is used for actions?

Yes.

Generally, I am interested in launching desktop programs directly into labwc without /bin/sh or other shell being used.

In line with this, I'm also interested in ability to launch a program by using a command-line command but again the idea would be that the program launches directly into labwc with no shell involved even though started from a command line in a shell. In this case, I would like the program to be process-owned by labwc and not the command shell that the command line was used in.

Could you describe the specific problem you are facing with? I cannot see what you want to achieve.

FYI, commands launched by labwc (e.g. from keybind action, menu action, autostart) are usually double-forked and they become child processes of systemd or other init system (a.k.a. orphan process). The command launched from labwc --session [command] is an exception; it becomes a direct child of labwc. It's also launched directly with execvp() without sh, so maybe this is what you want.

Can actions be defined in rc.xml then used directly as actions for keybinds and menu entries?

Yes, you can add <keybind><action name="Execute" command="[your command]"> in rc.xml or <menu><item><action name="Execute" command="[your command]"> in menu.xml.

[McPherran]

Thanks kindly for great info.

Labwc generally launches programs that way that I am interested in, i.e. without using sh <app_name>. So this is great! A specific feature of interest is start any program from command line...

... command launched from labwc --session [command] ... becomes a direct child of labwc. It's also launched directly with execvp() without sh, so maybe this is what you want.

...Yes. This is great information and a good example. However, I would like ability to have the same effect by using a command line command from within labwc (e.g. in Alacritty). A "run program" dialog is also fine, and hopefully the concept of a "run program" dialog is explanatory. If the program that is launched is process-owned by labwc, that is ideal, but if owned by systemd etc, that's OK too. The key is that I don't want the launched program to be owned by the command shell where the command to launch the program is entered. For example, in my terminal window (Alacritty, using ksh) I can run a web browser and /dev/null it and background it, &, but then if I run ps, I have all the clutter of the browser processes, and the browser is not disconnected from my Alacritty shell session. nohup works, but all the process clutter in ps remains.

(PS: I really like the workflow doors that the --session concept opens. Slightly different topic, but a great feature!)