Well find is an exact match... I use it to get the content of an album.
For mpd an album: "Eric Clapton - Unplugged" differs from "Eric Clapton
- unplugged" and treats it differently (also in the list command)
So handling that not-case-sensitive in just find is odd and breaks the
I also do queries with find on filename, (some places only filename is
stored) I don't want /Music/a/a.mp3 to be returned aswell when I
want /Music/A/a.mp3, it is a different file.
My point was (kind of), If you want todo something about case-sensitive
it should be done everywhere.
On Mon, 2008-02-11 at 10:48 -0700, Scott Horowitz wrote:
> On Feb 11, 2008 12:58 AM, Qball Cow <qball@...> wrote:
> > I am afraid how this will break the api and clients. mpd always was
> > case-sensitive, the list command is case-sensitive. making find then
> > not-case-sensitive might cause weird behavior.
> > More usefull might be making search support regex, so you can search for
> > ^REM$ or something like that (it's early)
> Did you mean to send this just to me? Also, search is not
> case-sensitive right now (and maybe list too?), only find is. I'm
> struggling to understand why any client dev would want a
> case-sensitive find result. Do you make use of it in gmpc?