Jason Spashett пишет:
> Alexander Belchenko wrote:
>> 2) Starting from 2.1 bzr parsing raw unsicode command-line string to be
>> able imitate glog expansion as on Linux, e.g.
>>
>> bzr status *.txt
>>
>> will show you status only for text files in the current directory.
>>
> Not sure why unicode is needed for (2), but it doesn't matter. Obviously
> there is a reason.
For emulating glob properly bzr needs to know about each argument: is
it was quoted or not. So
bzr ignore "*.obj"
won't expand wildcards and keep them as is. For this reason bzr needs
access to raw command-line string. Unicode is not required for this of
course.
Jason Spashett пишет:
> Alexander Belchenko wrote:
>> 2) Starting from 2.1 bzr parsing raw unsicode command-line string to be
>> able imitate glog expansion as on Linux, e.g.
>>
>> bzr status *.txt
>>
>> will show you status only for text files in the current directory.
>>
> Not sure why unicode is needed for (2), but it doesn't matter. Obviously
> there is a reason.
For emulating glob properly bzr needs to know about each argument: is
it was quoted or not. So
bzr ignore "*.obj"
won't expand wildcards and keep them as is. For this reason bzr needs
access to raw command-line string. Unicode is not required for this of
course.