Warmuptill
Active Member
Sorry to come back with yet another clarification question:OBS 30, yes, and the last adv-ss I tried was 1.23.1 which I updated to 1.24.0 and both worked fine before the OS update yes - to further clarify, it wasn't the major version upgrade. I had already done that and things were still working as of Silverblue 39.20231128.0 (2023-11-28T00:51:38Z).
The exact same OBS and plugin version caused crash with the newer OS version, right?
I think you are misunderstanding what the "Run" action is doing.I'm having a problem using the plugin's "Run" action. For example, I have a cmd command that I would like to run
How do I adapt this to the plugin's "Run" action?
The "Run" action is not launching the shell / command prompt of whichever OS you are using and then running the string you have passed to the "Run" action in that shell environment.
Instead is is simply trying to launching whichever executable file you pass to it with a given set of arguments.
This is why running shell specific built-in commands or keywords like
echo
, del
, <
, >
, |
, ... won't have any effect.If you do want to run shell commands with the "Run" action you can either put those commands in a script and run that instead or start the shell / command prompt binary itself and pass the commands you want to run as an argument.
For example, if you would want to use the
cmd.exe
shell environment to run the echo hi > someTextFile.txt
command you would have to start the cmd.exe
binary and pass /c
as the first argument and echo hi > someTextFile.txt
as the second argument.(See https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/cmd for a description of the arguments supported by cmd.exe)
You can set the folder in which the command should be executed using the "Working directory" field.Both commands take a specific folder to be executed.
The default working directory will be the folder in which the OBS binary is located at.
Hope that helps!
Let me know if you need further examples!
Last edited: