<whitequark[cis]1>
we don't necessarily have the best experience for programmatically launching an applet, but this is basically how you would do it yourself
<whitequark[cis]1>
a bit verbose
f_[m] has joined #glasgow
redstarcomrade has joined #glasgow
coderobe has joined #glasgow
Wanda[cis] has joined #glasgow
<Wanda[cis]>
so I got a documentation bug report, regarding memory-25x applet; the problem is that the documentation string talks of COPI/CIPO/WP/HOLD (and presents pinout accordingly), while the actual pins argument the applet takes is just called io and the correspondence between that and the presented pinout is not obvious unless you hold QSPI documentation in your hands
<whitequark[cis]1>
yes
<whitequark[cis]1>
can you fix that?
<Wanda[cis]>
should I just note the correspondence of COPI/... to IO0/IO1/IO2/IO3 in the docstring? I don't think we have a way to attach documentation to individual pin arguments?
<whitequark[cis]1>
i'd update the pinout in the docs too
<Wanda[cis]>
mhmm
<whitequark[cis]1>
and then explain in --pins-io help string the correspondence
<whitequark[cis]1>
(help="" should work, if it doesn't, add it to add_pin_argument)
<Wanda[cis]>
hmmm
<Wanda[cis]>
yeah, we don't have that yet
<Wanda[cis]>
... wtf is wrong with multidict again