----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> dee09247
@REPLY: <20230817065027.422@kylheku.com> 6fe801ef
@REPLYADDR David Brown <david.brown@hesbynett.no>
@REPLYTO 2:5075/128 David Brown
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References:
<9e7a4bd1-bfbb-4df7-af1a-27ca9625e50bn@googlegroups.com> <vo5rqj-lpl.ln1@paranoia.mcleod-schmidt.id.au> 1@dont-email.me>
1@milena.home.net.it> 1@news.xmission.com> 1@dont-email.me>
1@dont-email.me> <87o7j82gix.fsf@fatphil.org> 1@dont-email.me>
<20230817065027.422@kylheku.com>
@TZUTC: 0200
@PID: Mozilla/5.0 (X11; Linux x86_64; rv:102.0)
Gecko/20100101 Thunderbird/102.9.0
@TID: FIDOGATE-5.12-ge4e8b94
On 17/08/2023 15:52, Kaz Kylheku wrote:
> On 2023-08-17,
Muttley@dastardlyhq.com <
Muttley@dastardlyhq.com> wrote:
>> Any character from 0-255 is allowed in unix filenames but only an idiot would
>> use spaces and non printing characters.
Only an idiot would think one rule fits all use-cases.
>
> That`s simply false. 0 is the null terminator and is not actually part
> of the name. The path-component-separating slash cannot be contained in
> a path component; there is no escape mechanism to include it.
>
> POSIX defines a set of characters which are recommended for use in file
> names for portability; it is wise for applications and users to stick to
> that.
>
It is even wiser to use characters that are appropriate for the task in
hand.
If you are making software that will be shared amongst a wide variety of
systems, stick to ASCII letters, digits, and underscore - that will work
on everything, including Windows.
If you are writing a document in Thai that will be read by Thai speakers
on Thai computers, name the document in Thai using Thai script.
It`s not hard to handle "complicated" filenames from the command line,
outside a few pathological cases (like "-"). Sensible filenames are
fine, even with spaces, brackets, or non-ASCII letters. If those
features are helpful to the main use of the names for the files in
question, use them. If they are unhelpful, don`t use them.
Thus it makes sense to avoid inconvenient characters in the names and
paths of programs, and you`ll very rarely want them in program source
code names or directories. But they are common and useful for things
like document filenames.
--- Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5015/255 5019/40 5020/715 848
1042 4441 12000 5030/49 1081
SEEN-BY: 5075/128
@PATH: 5075/128 5020/1042 4441