Thanks for your bug report. As far as I can tell, this behaviour has been in place for a long time. It may be that isignore was updated at some point but the help file/online wikis were not. I have checked the ignore routine (it is pretty old code and has not been touched for at least a decade) and it looks like I should be able to update it to handle both switches and types without any side effects. This should be in the next version.
