On Sun, Feb 23, 2025 at 5:45 PM William Bader <williamba...@hotmail.com> wrote:
>
> Could you have a middle option to allow unicode in general that checks that
> $PWD does not contain certain characters while still blocking control
> characters and characters with special meanings in shells?
I will prefer to express what is allowed, and not what is not allowed.
This is because it is much easier for me to design tests based on the
allowed range and this way I do not forget any character.
So I might be able to do:
\p{L} - Matches any Unicode letter
\p{N} - Matches any Unicode number
\p{M} - Matches any Unicode mark (like diacritics)
and then make sure tests include these. In other words:
[-\p{L}\p{N}\p{M}_+,.%@:/= ]
I might also have to add () - I know that Firefox will happily make
files like: mydownload(1).zip so it is not unreasonable that users
expect dir names can also contain ().
I still need your guidance on whether GNU Parallel should refuse to
run without --unsafe (when detecting untested situations) or just
issue a warning or (like the old times) issue no warning.
/Ole
