So just a twist on this, several folks I know rename caches to allow smarter filtering and get information that is not available in a typical GPX transfer as fields may not be imported.  (as an example, counties in the US, reviewer, or placed month I commonly prepend.) This allows me to easily filter using the cache name after finding a cache that helps me with a challenge. This name editing will create an issue if cache name is used as a key and also which name to show.

Also another thought with the coloring is the original request asked about showing they are from different lists.  What about the case where a cache is in multiple lists and how to handle that?  

My workflow frequently has multiple lists for different challenges.  Combining them in a way that showed a cache was on 3 different lists would help me make progress on 3 challenges with one cache.  Filtering on that would also be nice.  

i like the idea.  Currently i use the offical app to do this from my phone.  

dont forget .zip files 

if there is a better way to phrase it let me know.  Wannabes?

is this really the precedent you want set?   everyone who doesnt use a tool downvotes it. 

also competing products open the file just fine.

sent via email as could not figure out in user echo

Understand all your comments but contains does not scratch my itch.

The problem I want to solve is separating a cache named "picklehopper -GCDROID is awesome" from "Thanks picklehopper". This is part of a trick used in my GPX files for challenge chasing where a county, reviewer, or other field is prepended to a cache name. And the things people make challenges from often appear in cache names.

The capability I really would like is "starts with".  Other cachers I know append at the end and want "ends with".

There have also been times on powertrails where the naming conventions have not been consistent and more flexibility would be appreciated. There have been changes in spaces around hyphens, missing hyphens, derivative caches nearby..

Regex seemed a good way to afford this flexibility. 

Just to be clear my suggestion was not that regex be the default but an option available for power users.

There are a couple of options:

Make the default to do the promotion but it can be turned off.

Another is to Make this a feature one can pay to turn off.