This depends on #105 (and fixes for bash <4) to some extent: If HISTCONTROL is set in such a way that ignorespace is not implied, #mcfly: debris will pollute history. This is not as bad as it seems, becuase it is still be possible for users to create this issue by setting a bad HISTCONTROL after loading mcfly.bash in their .bashrc.
Otherwise, checks can be added for specific $HISTCONTROL values. In my case, my ignoreboth (which implies ignorespace) was being overwritten.
cantino
commented
3 years ago
This depends on #105 (and fixes for
bash <4) to some extent: If HISTCONTROL is set in such a way thatignorespaceis not implied,#mcfly:debris will pollute history. This is not as bad as it seems, becuase it is still be possible for users to create this issue by setting a badHISTCONTROLafter loadingmcfly.bashin their.bashrc.Otherwise, checks can be added for specific
$HISTCONTROLvalues. In my case, myignoreboth(which impliesignorespace) was being overwritten.