On Sun, 2026-02-22 at 01:18 +0100, Simon Iten wrote: > > However if I send multiple pinctrl commands in a short timespan some > are dropped.
Yeah, [shell] can only execute one command at the time. When [shell] is still busy with the last command, it'll simply ignore the current call. Anyway, you may want to try [command] which is a fork of [shell] with more features. [command] outputs the exit code when the execution of the command has completed. However, you still need to buffer your calls so that they are executed one after another. You'll find [command] in Deken. > Also, running pinctrl set 5.6.13 op dl for example does not work (it > should pull low those three outputs at once and works in the terminal > just fine) But PD also automagically adds spaces after the commas > once the message box is not edited anymore. That's not a [shell] specific issue, but is how Pd parses messages in general. A comma in message box is actually a delimiter for messages. By using unescaped commas you actually create multiple messages 'pinctrl set 5', '6', and '13 op dl'. 'exec pinctrl set 5\,6\,13 op dl' seems to work with [command] > > Are these known limitations of shell or is there a workaround to run > multiple commands at once? Adding & or ; to the end of the message > sent to shell does not work... I don't know about &, but ';' is also a Pd delimiter for sending messages. Roman
signature.asc
Description: This is a digitally signed message part
--- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/H73WUW7EJCZHUG3YWZLTJAPJLW6ETM4P/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
