No, and I'm highly skeptical it'll achieve what I'm looking for. Can you give an example of what you mean? How do I search for "ATXMEGA*D3" and get "ATXMEGA64D3", "ATXMEGA128D3", "ATXMEGA256D3", etc to come up?
On Fri, Dec 18, 2015 at 12:14:33PM -0500, Jon Evans wrote: > More and more modern text editing software is moving to fuzzy string > matching rather than explicitly requiring users to put in wildcards when > doing searches for filenames, code intelligence searches (i.e. match > function / class names etc). Have you considered that as an option? > > On Fri, Dec 18, 2015 at 12:08 PM, Chris Pavlina <[email protected]> > wrote: > > > Would everyone be okay with me patching the eeschema component chooser > > to support wildcards or regexes? And if yes, what's the preference - > > simple *? wildcards, regexes, or selectable in preferences? (Plan is to > > make it totally disableable [is that a word? :] in prefs anyway.) > > > > -- > > Chris > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
