[RFC] handling files with weird names in .bzrignore

[Stefan Monnier]

>> Feeping creaturism.  Why not just add a --noglob argument to "bzr
>> ignore" which will then turn the pattern into an "RE:" pattern with the
>> needed escaping?
> Because that means typing '--noglob' instead of 'RE:' ? 

Then type "RE:": I'm not suggesting to get rid of that one, but for
those people who don't want to remember which chars need escaping and
how to escape, it can be convenient to have a --noglob that does it
for them.

>>> (4) When turning patterns into regexes, anything that is illegal just
>>> gets thrown out with a warning saying that it isn't a legal pattern.
>> Yes: that's really the only solution that's possible, reliable, and safe.
> But I think you imply there that you don't consider the --noglob option
> really needed ?

Indeed, it's not really needed: the invalid entry will trigger a warning
as soon as it gets used anyway.

> I.e. if an argument is neither a valid glob nor a valid regexp, warn.

It might be good to have "bzr ignore" warn (or even signal an error)
right away rather than wait for the warning to come later when the
invalid entry is used, but it's fairly minor compared to the issue of
fixing the current behavior.


        Stefan