I was under the impression that "/+shoot2 1" should turn on your primary mining beams, and "/+shoot 2 0" should turn them off again?

Do I have this wrong? As per the documentation:
# the below plus commands can be turned off by releasing the key
# it is bound to or by typing an extra separated 0 at the end
# ex1: /+Accelerate 0
# ex2: alias turbo_off "+Turbo 0"

What I'm finding in practice is that "/+shoot2 1" will turn them on. Repeated entries of "/+shoot2 1" leave them on.

Entering "/+shoot2 0" leaves them on.

After entering "/+shoot2 0", "/+shoot2 1" will turn them off again. Repeated entries of "/+shoot2 1" leave them off at this point.

Upon entering "/+shoot2 0" again, "/+shoot2 1" will turn them back on, behavior repeats.

"/+Shoot2 1" is the same as holding down the primary trigger, and "+Shoot2 0" releases it.

For mining beams you don't have to hold the trigger down -- you click once to start them and click again to turn them off. It makes sense to do "/+Shoot2" and "/+Shoot2 0" to start the beams followed by "/+Shoot2" and "/+Shoot2 0" again to turn them off.

Hm, yeah, that makes sense! Thank you, meridian!

---------------------------------------------------------------

I guess I should mention that part of why I brought this up comes from the M.A.I.D. plugin source code...

It looks like the command for releasing the trigger again after turning off the beams is commented out? What's up with that? (Code snippet below, for reference)

---------------------------------------------------------------

From M.A.I.D.:

function MAID:disableBeamAtPort(portid)
[...code...]
-- the below commands are the equivalent of setting the proper group,
-- pressing the fire button and releasing the fire button
gkinterface.GKProcessCommand('weapon'..weapongroup)
gkinterface.GKProcessCommand('+Shoot'..trigger..' 1')

-- For some reason, we can't simulate the key release!?
--gkinterface.GKProcessCommand('+Shoot'..trigger..' 0')
^^^^^^ ?

+ commands are not handled the same way as normal commands, the syntax when using + changes a bit. It's not /+shoot2 1, just /+shoot2 and the reverse (ie to turn it off) is /-shoot2.

/+shooot2 == /shoot2 1 : /-shoot2 == /shoot2 0