I spent many years in a UNIX environment, where it was common to use regular expressions on text files. That was some time ago, and with CRS, there are only a few features I can use without documentation. (sigh)

>>Which is exactly why I would use a regular expression to do the searching (in Code References, where it is available) which allows you to catch all of the various combinations.
>
>I was thinking about that, but also of http://xkcd.com/208/ - it just came coming to mind :).
>
>>I've always thought that the absence of regular expressions in the Ctrl+F for methods to be a serious mistake.
>
>When it was written, regular expressions were probably PhD stuff. Too bad it wasn't updated - then I'd have learned them by now :). As it is, I re-learn some of it every year, again and again.
>
>>>>I also tend to do searches, whether it be using Code References or Ctrl+F, and the second syntax makes assignments harder to find. (I can search for 'x = ' easily enough, but it's much harder to see how to search for assignments using the second alternative.)
>>>
>>>Actually, searching for "x=" is equally easy as searching for "x =" and "x{tab}="... and all three are valid, and (depending on coding style) more or less possible to find in code. So instead of three, you need to search for four.
>>>
>>>But I'd never search for x=. Too short a name for a variable.