Thanks for mentioning this. Unfortunately, pattern matching still
uses old code and this code has rather peculiar handling of
underscores, in particular signaling errors like this. Probably
the simplest way to fix such problems is to write new pattern
matching code. I concentrated my attention on different problems,
but probably it is time to handle this one too.
BTW: old browse code had alternative paths, so such patterns
sometimes worked, but new code is simpler and in particular
'search_operations' has no alternative paths, it always is
doing the same thing (that is match pattern to each operation
name).
--
Waldek Hebisch