Greg Shenaut wrote:
>
> Right. Easiest is not necessarily best, in this case for exactly
> your reason. If you want a space in a filename, the Unix tradition
> clearly favors your having one.
>
> But you have to admit, space is a character that has caused many
> problems in Unix filenames, bec
Greg Shenaut <[EMAIL PROTECTED]> types:
> In message <[EMAIL PROTECTED]>, void cleopede:
> >On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote:
> >> Is there any reason why the "unbreakable space" (0xa0) shouldn't be
> >> the only kind of space character used/allowed in filenames?
> >Any
In message <[EMAIL PROTECTED]> Greg Shenaut writes:
: But you have to admit, space is a character that has caused many
: problems in Unix filenames, because of the other Unix tradition of
: space-delimited word record handling. I usually use an underscore,
: myself, if I want a space-like separat
In message <[EMAIL PROTECTED]> Giorgos Keramidas writes:
: Greg Shenaut <[EMAIL PROTECTED]> wrote:
: >
: > I just throw out the idea--as for where to enforce such a convention,
: > I agree that the file-system definition may not be the best place,
: > but it might be the *easiest* place (spaces c
In message <[EMAIL PROTECTED]>, Giorgos Keramidas cleopede:
>Greg Shenaut <[EMAIL PROTECTED]> wrote:
>>
>> Just out of curiosity, what would be an instance where you have
>> wanted a space in a filename and wouldn't have been satisfied with
>> 0xa0 instead of 0x20?
>
>All of them. Space is so co
Greg Shenaut <[EMAIL PROTECTED]> wrote:
>
> Just out of curiosity, what would be an instance where you have
> wanted a space in a filename and wouldn't have been satisfied with
> 0xa0 instead of 0x20?
All of them. Space is so conveniently placed under the tip of my thumb.
To type 0xa0 I would h
In message <[EMAIL PROTECTED]>, Giorgos Keramidas cleopede:
>Greg Shenaut <[EMAIL PROTECTED]> wrote:
>>
>> I just throw out the idea--as for where to enforce such a convention,
>> I agree that the file-system definition may not be the best place,
>> but it might be the *easiest* place (spaces cou
Greg Shenaut <[EMAIL PROTECTED]> wrote:
>
> I just throw out the idea--as for where to enforce such a convention,
> I agree that the file-system definition may not be the best place,
> but it might be the *easiest* place (spaces could be silently mapped
> to 0xa0's).
Please don't even think abou
In message <[EMAIL PROTECTED]>, void cleopede:
>On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote:
>>
>> Is there any reason why the "unbreakable space" (0xa0) shouldn't be
>> the only kind of space character used/allowed in filenames?
>
>Any character except for '/' is allowed in file
On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote:
>
> Is there any reason why the "unbreakable space" (0xa0) shouldn't be
> the only kind of space character used/allowed in filenames?
Any character except for '/' is allowed in filenames, and I believe it's
been that way since the daw
In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" cleopede:
>Stijn Hoop wrote:
>>
>> > Any way using `` won't work. for i in a "b c" d works, for instance, but
>> > there is not way that I know of that you can control the output this way
>> > using ``.
>>
>> Yes there is: set IFS to only contai
11 matches
Mail list logo
