I know that "non-steam" is not the priority, and I am not demanding that non-steam options be given any kind of priority. But it's still functionality available to users, so refinements aren't completely nonsensical. IMO.
Definitely related, however 4666 looks like this, but inverted - multiple entries to the same executable (file) there, vs one entry with [1..n] options here.
Obviously n should not be insane, but you get the point.
I would also very much like the ability to have multiple launch options for non-steam games...
In the same manner Vampire Survivors (a steam game) can prompt the user which Launch Options to start with:
i want too on Steam-Deck for game collection y have
Nothing extracted yet.
Scenario
Given a Linux, or Deck, system, and non-Steam applications / games of any kind, sometimes a given app/launcher/game may have additional command-line options to enhance, speed up, or otherwise change the target's launch behaviour.
--run-gameargumentRequest: Multiple Launch Options
Much like existing entries' launch configs (Hades is such an example), let users add multiple launch entries to locally-configured apps/launchers/games (along with a Default setting, but I think that's coming?)
System information