Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Oct 2020 13:25:16 +0200
From:      Ralf Mardorf <ralf-mardorf@riseup.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: sh scripting question
Message-ID:  <20201016132516.71e06c69@archlinux>
In-Reply-To: <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com>
References:  <d50ba2c9-617f-6842-ef89-f5933be8f8b3@hotmail.com> <DB8PR06MB64427D88E17F02711EE657A3F6030@DB8PR06MB6442.eurprd06.prod.outlook.com> <20201016113408.16d58d68@archlinux> <DB8PR06MB644292D3C0309B5DADADF69BF6030@DB8PR06MB6442.eurprd06.prod.outlook.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, 16 Oct 2020 15:55:59 +0530, Manish Jain wrote:
>Hi Ralf,
>
>This is where I actually have an entirely different philosophy. When
>you create a file with a leading - (or for that matter, weird
>characters such as * anywhere in the filename) [snip]

I can't notice a different philosophy. We agree again. I just wanted to
point out, that our scripts might need to be able to handle some
imported iDroidWindowsCamEmailAttachment file names, at least to some
extend, but we and anybody using systems we might administrate, should
apply a minimum of convention, compatibility, portability.

Let alone that a apart from little girls nobody tend to name a file

***such a cute cat ;)...

and only complete unworldly users use uninformatively names such as

-*.

On the quick I was unable to create a file with a

/

in it's name (Linux, login shell bash, just using shell commands, no
tool explicitly aimed to edit/corrupt file system entries). I guess a
file name containing a "/" overTRUMPs all other odd file names.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20201016132516.71e06c69>