Problems with colons in searches

[JB Caruth]

On Thu, May 22, 2014 at 5:49 PM, Jeremy Nicoll - ml get_iplayer
<jn.ml.gti.91 at wingsandbeaks.org.uk> wrote:

> The results seem to be those of
>
>     $ ./get_iplayer ^Coast
>
> which makes me wonder if ":" has some meaning in whatever command shell you're using?

Ok - yes - that makes sense - thanks - I don't often run manual
searches so I forgot to quote the search regex - it was splitting the
search on spaces into three values.

Running again (as I intended) with quotes I get the same results as
the PVR search (no programmes found) - truncated verbose output below:

> $ ./get_iplayer "^Coast\: Coast Australia$" --verbose
> get_iplayer v2.86, Copyright (C) 2008-2010 Phil Lewis
> INFO: Search args: '^Coast\: Coast Australia$'
> INFO: Got 3459 file cache entries for tv
> INFO: Search term '^Coast\: Coast Australia$' is a substring
> DEBUG: Search download_regex = ^Coast\: Coast Australia$
> INFO: 0 Matching Programmes

The same command without the escaped ":" also finds no programmes
(truncated verbose output below):

> $ ./get_iplayer "^Coast: Coast Australia$" --verbose
> INFO: Search args: '^Coast: Coast Australia$'
> INFO: Got 3459 file cache entries for tv
> INFO: Search term '^Coast: Coast Australia$' is a substring
> DEBUG: Search download_regex = ^Coast: Coast Australia$
> INFO: 0 Matching Programmes

Which leaves me back where I started - wondering why the search (via
PVR or manual, with or without escaped colon) is not finding the
available programmes.