On Mon, Dec 12, 2005 at 08:17:18AM -0800, Brian Dessent wrote:
>Christopher Faylor wrote:
>>but I don't think we should ever go down the path of blithely creating
>>files with special characters by default.
>
>Now, now... what better way to embrace WJM at its finest than for
>Cygwin to randomly an
On Dec 12 08:17, Brian Dessent wrote:
> Christopher Faylor wrote:
>
> > but I don't think we should ever go down the path of blithely creating files
> > with special characters by default.
>
> Now, now... what better way to embrace WJM at its finest than for Cygwin
> to randomly and inexplicably
Christopher Faylor wrote:
> but I don't think we should ever go down the path of blithely creating files
> with special characters by default.
Now, now... what better way to embrace WJM at its finest than for Cygwin
to randomly and inexplicably litter stray "CON" or "you can't delete me
. . . " f
On Mon, Dec 12, 2005 at 10:49:52AM +0100, Corinna Vinschen wrote:
>On Dec 8 23:50, Brian Dessent wrote:
>> Yitzchak Scott-Thoennes wrote:
>>
>> > > Windows strips trailing spaces and dots (unless the file name
>> > > consists only of spaces). You need a managed mount to
>> > > preserve those; ot
On Dec 8 23:50, Brian Dessent wrote:
> Yitzchak Scott-Thoennes wrote:
>
> > > Windows strips trailing spaces and dots (unless the file name
> > > consists only of spaces). You need a managed mount to
> > > preserve those; otherwise "foo ", "foo.", "foo. . . . ", "foo",
> > > and a bunch of other
Yitzchak Scott-Thoennes wrote:
> > Windows strips trailing spaces and dots (unless the file name
> > consists only of spaces). You need a managed mount to
> > preserve those; otherwise "foo ", "foo.", "foo. . . . ", "foo",
> > and a bunch of other spellings all refer to the same file.
>
> I atte
On Fri, Dec 09, 2005 at 12:31:32AM +, Eric Blake wrote:
> From: Yitzchak Scott-Thoennes <[EMAIL PROTECTED]>
> >
> > Moving on to another "non-portable" problem, I want to create a file
> > with a space at the end of the name, but cygwin is stripping spaces.
> > Despite the comment in the code,
From: Yitzchak Scott-Thoennes <[EMAIL PROTECTED]>
>
> Moving on to another "non-portable" problem, I want to create a file
> with a space at the end of the name, but cygwin is stripping spaces.
> Despite the comment in the code, this does seem to be allowed (though
> I suspect it may be via NtCrea
On Fri, Dec 02, 2005 at 11:09:05PM +0100, Corinna Vinschen wrote:
> On Dec 2 20:38, Eric Blake wrote:
> > > I'm trying to create a file (on NTFS) with a CR in the name and getting
> > > ENOENT; is it possible for this to work (without a managed mount)?
> >
> > Welcome to Windows. None of these n
On Dec 5 11:20, Bill Hughes wrote:
> I'm not sure it would be obvious that the FS is capable of case sensitive
> operations if we didn't already know that - to me it's equally obvious that
> FAT
> isn't capable of these. Unless I'm wrong again of course.
Well, the GetVolumeInformation function r
Corinna Vinschen cygwin.com> writes:
>
> On Dec 5 10:11, Bill Hughes wrote:
..snip..
> > Uh, don't forget this is the NTFS API and not the Windows API.
> > If you want to go down this route you may as well add case sensitive file
> > names too...
>
> That's not quite right. Case-sensitivity i
On Dec 5 10:11, Bill Hughes wrote:
> Corinna Vinschen cygwin.com> writes:
>
> >
> > On Dec 4 09:29, Yitzchak Scott-Thoennes wrote:
> ..snip..
> > >
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
> > > is interesting...
> >
> > This is certainly interesting. Using this
Corinna Vinschen cygwin.com> writes:
>
> On Dec 4 09:29, Yitzchak Scott-Thoennes wrote:
..snip..
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
> > is interesting...
>
> This is certainly interesting. Using this in Cygwin would require to
> change the path handling to
On Sun, 4 Dec 2005, Corinna Vinschen wrote:
http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
is interesting...
This is certainly interesting. Using this in Cygwin would require to
change the path handling to using UNICODE, though, which is a major
undertaking since the path han
On Dec 4 09:29, Yitzchak Scott-Thoennes wrote:
> On Fri, Dec 02, 2005 at 11:09:05PM +0100, Corinna Vinschen wrote:
> > On Dec 2 20:38, Eric Blake wrote:
> > > > I'm trying to create a file (on NTFS) with a CR in the name and getting
> > > > ENOENT; is it possible for this to work (without a manag
On Fri, Dec 02, 2005 at 11:09:05PM +0100, Corinna Vinschen wrote:
> On Dec 2 20:38, Eric Blake wrote:
> > > I'm trying to create a file (on NTFS) with a CR in the name and getting
> > > ENOENT; is it possible for this to work (without a managed mount)?
> >
> > Welcome to Windows. None of these n
On Dec 2 20:38, Eric Blake wrote:
> > I'm trying to create a file (on NTFS) with a CR in the name and getting
> > ENOENT; is it possible for this to work (without a managed mount)?
>
> Welcome to Windows. None of these non-portable characters are
> supported in filenames except in managed mounts
> I'm trying to create a file (on NTFS) with a CR in the name and getting
> ENOENT; is it possible for this to work (without a managed mount)?
Welcome to Windows. None of these non-portable characters are
supported in filenames except in managed mounts.
--
Eric Blake
--
Unsubscribe info:
I'm trying to create a file (on NTFS) with a CR in the name and getting
ENOENT; is it possible for this to work (without a managed mount)?
Trying all possible characters:
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv)
{
int fd, c, err;
char filena
19 matches
Mail list logo
