On Fri, Oct 10, 2008 at 9:22 AM, Branko Èibej <brane_at_xbc.nu> wrote:
> Mark Phippard wrote:
>> On Fri, Oct 10, 2008 at 9:04 AM, Branko Èibej <brane_at_xbc.nu> wrote:
>>
>>> Mark Phippard wrote:
>>>
>>>> Sorry for the drive-by, but this just popped into my head as I was
>>>> thinking about the wc-ng stuff a bit.
>>>>
>>>> I believe one of the changes going into 1.6 has to do with the
>>>> management of the text-base (using SQLite). I was wondering if that
>>>> included discontinuing the use of the file name in the name of the
>>>> file in text-base? If we did this, that would presumably resolve the
>>>> case-sensitivity problems we have on Windows and OSX.
>>>>
>>>>
>>> It would resolve some of the case-sensitivity problems, yes. It won't
>>> solve the "files in same dir differ only in case" issue, nor the nastier
>>> one where the user (or some tool) changes the case of a filename in the
>>> WC and then we don't find the file in entries any more. And note that
>>> these are not limited to Windows amd Mac, they can happen, e.g., on
>>> Linux on a case-insensitive filesystem (e.g., FAT, or CIFS mount).
>>>
>>
>> True, thanks for pointing this out. It will only solve the issue of
>> letting you rename a file where you only change the case.
>>
>
> Will it? I think current WC code still stats the rename destination and
> cries if it finds it.
Don't know. With current code it fails when it tries to create the
text-base and a file of the same name already exists. So I assumed if
that is fixed then the rest would work.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2008-10-10 15:24:47 CEST