On Wed, Dec 11, 2013 at 06:01:03PM +0100, Corinna Vinschen wrote:
>>Perhaps this will require reiteration and reclarification on Thursday,
>>feline-permitting.
>
>And it's not even my WJM week. Can we move that to Thursday next week?
Sorry, no. I can't allow that. But, then, it's my week.
cgf
On Dec 11 11:30, Christopher Faylor wrote:
> On Wed, Dec 11, 2013 at 05:21:37PM +0100, Corinna Vinschen wrote:
> >On Dec 11 19:27, Mikhail Usenko wrote:
> >> On Wed, 11 Dec 2013 16:23:39 +0100
> >> Corinna Vinschen <...> wrote:
> >>
> >> > On Dec 11 19:02, Mikhail Usenko wrote:
> >> > > I couldn't
On Wed, Dec 11, 2013 at 05:21:37PM +0100, Corinna Vinschen wrote:
>On Dec 11 19:27, Mikhail Usenko wrote:
>> On Wed, 11 Dec 2013 16:23:39 +0100
>> Corinna Vinschen <...> wrote:
>>
>> > On Dec 11 19:02, Mikhail Usenko wrote:
>> > > I couldn't figure out how a POSIX filename passed to a Cygwin
>> >
On Dec 11 19:27, Mikhail Usenko wrote:
> On Wed, 11 Dec 2013 16:23:39 +0100
> Corinna Vinschen <...> wrote:
>
> > On Dec 11 19:02, Mikhail Usenko wrote:
> > > I couldn't figure out how a POSIX filename passed to a Cygwin
> > > application running on the Windows system may become longer than
> > >
On Wed, 11 Dec 2013 16:23:39 +0100
Corinna Vinschen <...> wrote:
> On Dec 11 19:02, Mikhail Usenko wrote:
> > I couldn't figure out how a POSIX filename passed to a Cygwin
> > application running on the Windows system may become longer than
> > NAME_MAX=1020 bytes if the maximum filename length in
On Dec 11 19:02, Mikhail Usenko wrote:
> I couldn't figure out how a POSIX filename passed to a Cygwin
> application running on the Windows system may become longer than
> NAME_MAX=1020 bytes if the maximum filename length in NTFS is 255
> UTF-16 symbols (i.e. 1020 bytes for the biggest 4 byte UTF-
I couldn't figure out how a POSIX filename passed to a Cygwin application
running on the Windows system may become longer than NAME_MAX=1020 bytes if the
maximum filename length in NTFS is 255 UTF-16 symbols (i.e. 1020 bytes for the
biggest 4 byte UTF-8 code unit)?
What causes the ENAMETOOLONG
On Dec 11 17:49, Mikhail Usenko wrote:
> On Tue, 10 Dec 2013 11:27:55 +0100
> Corinna Vinschen <...> wrote:
>
>
> > Easier said than done.
> >
> > Cygwin is using the native NT API
> > and, occasionally, the Win32 UNICODE file API, which allows paths of up
> > to 32767 chars.
> > ...
> > How do
On Tue, 10 Dec 2013 11:27:55 +0100
Corinna Vinschen <...> wrote:
> Easier said than done.
>
> Cygwin is using the native NT API
> and, occasionally, the Win32 UNICODE file API, which allows paths of up
> to 32767 chars.
> ...
> How do you represent this in a byte-oriented POSIX system? What do
On Dec 11 11:04, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > The problem here is about NAME_MAX. NAME_MAX is per POSIX[1] the
> > "maximum number of bytes in a filename (not including the terminating
> > null)."
>
> Does this mean that POSIX standard is not compatible with real life
Greetings, Corinna Vinschen!
>> >Sorry if that is frustrating in your current situation, but this
>> >isn't something we can just change at a whim and go ahead. It
>> >would break compatibility with all existing Cygwin executables.
>>
>> Maybe this is something that could be fixed only in the 64-
Greetings, Corinna Vinschen!
> The problem here is about NAME_MAX. NAME_MAX is per POSIX[1] the
> "maximum number of bytes in a filename (not including the terminating
> null)."
Does this mean that POSIX standard is not compatible with real life?
No surprise I was having hard times copying a rat
On Tue, Dec 10, 2013 at 04:32:59PM +0100, Corinna Vinschen wrote:
>On Dec 10 16:48, Noel Grandin wrote:
>>On 2013-12-10 12:27, Corinna Vinschen wrote:
>>>Sorry if that is frustrating in your current situation, but this isn't
>>>something we can just change at a whim and go ahead. It would break
>>
On Dec 10 16:48, Noel Grandin wrote:
> On 2013-12-10 12:27, Corinna Vinschen wrote:
> >Sorry if that is frustrating in your current situation, but this
> >isn't something we can just change at a whim and go ahead. It
> >would break compatibility with all existing Cygwin executables.
>
> Maybe this
On 2013-12-10 12:27, Corinna Vinschen wrote:
Sorry if that is frustrating in your current situation, but this isn't something we can just change at a whim and go
ahead. It would break compatibility with all existing Cygwin executables.
Maybe this is something that could be fixed only in the 64-
On Dec 10 11:15, Nikolay Ilychev wrote:
> Hello!
>
> When using cygwin, i can't list, copy, remove files and directories
> with 128 utf-8 symbol long names.
>
> useless examples that illustrates the problem:
> [...]
> same problem with other tools - find, perl, rsync from cygwin repo.
>
> Please
Greetings, Nikolay Ilychev!
> Please, make the MAX_PATH not for 260 bytes, but 260 utf-8 symbols.
You can't just "make MAX_PATH", this is an Operating System (i.e. Windows, not
Cygwin) constant.
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 10.12.2013, <13:37>
Sorry for my terrible english...
-
17 matches
Mail list logo
