On Wed, Jan 7, 2009 at 7:31 AM, Alexandre Julliard wrote:
> Vitaliy Margolen writes:
>
>> Alexandre Julliard wrote:
>>> The problem is not Unix paths, it's usually that the app expects the
>>> current directory to be the app directory. You have the same issue if
>>> you use a Windows path. If the
Alexandre Julliard wrote:
> "Austin English" writes:
>
>> On Tue, Jan 6, 2009 at 9:07 PM, James Hawkins wrote:
>>> On Tue, Jan 6, 2009 at 7:04 PM, Austin English
>>> wrote:
Adds a note discouraging use of UNIX paths, since there's seems to
have been a rash of it in recent bug reports
Vitaliy Margolen writes:
> Alexandre Julliard wrote:
>> The problem is not Unix paths, it's usually that the app expects the
>> current directory to be the app directory. You have the same issue if
>> you use a Windows path. If there are really issues caused by argv[0]
>> being a Unix path and no
"Austin English" writes:
> On Tue, Jan 6, 2009 at 9:07 PM, James Hawkins wrote:
>> On Tue, Jan 6, 2009 at 7:04 PM, Austin English
>> wrote:
>>> Adds a note discouraging use of UNIX paths, since there's seems to
>>> have been a rash of it in recent bug reports.
>>
>> If we don't recommend it, a
On Tue, Jan 6, 2009 at 9:07 PM, James Hawkins wrote:
> On Tue, Jan 6, 2009 at 7:04 PM, Austin English
> wrote:
>> Adds a note discouraging use of UNIX paths, since there's seems to
>> have been a rash of it in recent bug reports.
>>
>
> If we don't recommend it, and usually advise against it, wh
On Tue, Jan 6, 2009 at 7:04 PM, Austin English wrote:
> Adds a note discouraging use of UNIX paths, since there's seems to
> have been a rash of it in recent bug reports.
>
If we don't recommend it, and usually advise against it, why not just
remove that line from the README?
--
James Hawkins
