Development record
The kill-by-pattern and kill-by-name blockers never fire when the pattern arrives through a command substitution: an unquoted substitution contributes no word under the vanish reading, so the operand count the min_operands constraint reads is zero and pkill or killall with its pattern substituted in is allowed. A substitution standing as its own word is one operand of unknown text for that count. Found by review-guard finding 3.
issueresolvedmajoriss-2609251640353017
The kill-by-pattern and kill-by-name blockers never fire when the pattern arrives through a command substitution: an unquoted substitution contributes no word under the vanish reading, so the operand count the min_operands constraint reads is zero and pkill or killall with its pattern substituted in is allowed. A substitution standing as its own word is one operand of unknown text for that count. Found by review-guard finding 3.
Grounds
- pursued: pkill and killall with the pattern substituted in block, while the group and parent selectors fed by a substitution stay allowed and positional compares keep the vanish reading; an allow of a substituted pattern, or a block of a substituted group id, would show it wrong
Frontmatter
| id | iss-2609251640353017 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2609251640353017-the-kill-by-pattern-and-kill-by-name.md
open on GitHub ↗ · commit history ↗