Console output messages for 'Detected:' messages not complete

[jngreene]

for example:
I have a rule:

warp [one,two,three,four,five,six,seven,eight]

when I say 'warp five' stdout shows:

Detected: warp

It should read

Detected: warp five

or worst case

Detected: warp [one,two,three,four,five,six,seven,eight]
'''
I'm researching the code fix to submit with this but have not found the mojo yet.

[jngreene]

Okay, it looks like this is a side effect of making all square brackets optional. I propose that instead of all square brackets being optional it would be easier to make square brackets optional only if the square bracket contain a blank option:
Multi option square bracket no blank option:

[one,two, three,four , five ,six]

Multioption with blank option(s) rendering the contents optional

[,one,two,three,four,five,six]
[one,,two,three,four,five,six]
[ ,one,two,three,four,five,six]
[one, ,two,three,four,five,six]
[one,two,three,four,five,six,]
[one ,two ,three ,four ,five ,six, ]

thus you could change:

#  file profileexecutor.py
# subtract lines:102 through 103
        if variation:  # Only add non-empty variations
            variations.append(variation)

Thus the following cases would occur:

rule title: warp [one,two,three,four,five,six,seven,eight] 
rule title: warp nine

would generate command variants:

warp one
warp two
warp three
warp four
warp five
warp six
warp seven
warp eight
warp nine

This would prevent my current issue where the first command also creates a variant 'warp' which prevents 'warp nine' from ever matching unless I specify nine separate rules instead of two. It would also still allow to create such an error with

rule title: warp [,one,two,three,four,five,six,seven,eight] 
rule title: warp nine

I realize now that I could fix this with a

rule title: warp one,warp two,warp three,warp four,warp five,warp six,warp seven,warp eight
rule title: warp nine

I submit that logically, one would want at least one of the options within the brackets to be matched, including a blank option. Thus assuming a blank option is logically erroneous.*(Hence the need programmatic logic for deliberately parsing out a blank option when assuming all are optional). Removing those two lines and the checking of [0] for an optional versus static rather than segment number would provide the necessary functionality and enable the storing of those options as command segments for use in comparisons and control loops within rules. Or should I just fork?