On Mon, Dec 6, 2010 at 5:45 PM, Peter Hutterer peter.hutte...@who-t.net wrote:
On Mon, Dec 06, 2010 at 05:47:02AM -0800, Dan Nicholson wrote:
On Sun, Dec 5, 2010 at 9:29 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, Dec 02, 2010 at 06:19:15AM -0800, Dan Nicholson wrote:
The
On Tue, Dec 07, 2010 at 06:03:53AM -0800, Dan Nicholson wrote:
On Mon, Dec 6, 2010 at 5:45 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Mon, Dec 06, 2010 at 05:47:02AM -0800, Dan Nicholson wrote:
On Sun, Dec 5, 2010 at 9:29 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Sun, Dec 5, 2010 at 9:29 PM, Peter Hutterer peter.hutte...@who-t.net wrote:
On Thu, Dec 02, 2010 at 06:19:15AM -0800, Dan Nicholson wrote:
The InputClass Match* entries are currently hardwired to offer a certain
variant of comparison for matching. For example, the MatchProduct entry
uses
On Mon, Dec 06, 2010 at 05:47:02AM -0800, Dan Nicholson wrote:
On Sun, Dec 5, 2010 at 9:29 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, Dec 02, 2010 at 06:19:15AM -0800, Dan Nicholson wrote:
The InputClass Match* entries are currently hardwired to offer a certain
variant of
On Thu, Dec 02, 2010 at 06:19:15AM -0800, Dan Nicholson wrote:
The InputClass Match* entries are currently hardwired to offer a certain
variant of comparison for matching. For example, the MatchProduct entry
uses substring match. Add a second optional argument to the entry to
allow the match
The InputClass Match* entries are currently hardwired to offer a certain
variant of comparison for matching. For example, the MatchProduct entry
uses substring match. Add a second optional argument to the entry to
allow the match type to be specified.
MatchProduct foo* pattern
The
