Date: Tue, 15 Oct 2024 10:47:47 -0400
On Tue, Oct 15, 2024 at 10:12 AM René Ferdinand Rivera Morell <
grafikrobot_at_[hidden]> wrote:
> On Tue, Oct 15, 2024 at 9:08 AM Steve Downey via SG15
> <sg15_at_[hidden]> wrote:
> >
> > You might consider restricting the first character, which must exist, to
> [a-zA-Z] to avoid things getting confused by a leading `-`.
> > Might also consider . and : for otherwise meaningless namespacing
> conventions, similar to the meaningless ones for modules?
>
> As ":" is problematic in the Windows ecosystem command lines, and
> these are likely to end up as CLI args, I would avoid anything
> "fancy".
>
> Will Windows shells do stuff to things that look like device names or
drives? They're in URLs and that would seem a more common problem. But if
it's a problem, it's a problem, and since it's not necessary, it's easier
to not allow.
>
> --
> -- René Ferdinand Rivera Morell
> -- Don't Assume Anything -- No Supone Nada
> -- Robot Dreams - http://robot-dreams.net
>
grafikrobot_at_[hidden]> wrote:
> On Tue, Oct 15, 2024 at 9:08 AM Steve Downey via SG15
> <sg15_at_[hidden]> wrote:
> >
> > You might consider restricting the first character, which must exist, to
> [a-zA-Z] to avoid things getting confused by a leading `-`.
> > Might also consider . and : for otherwise meaningless namespacing
> conventions, similar to the meaningless ones for modules?
>
> As ":" is problematic in the Windows ecosystem command lines, and
> these are likely to end up as CLI args, I would avoid anything
> "fancy".
>
> Will Windows shells do stuff to things that look like device names or
drives? They're in URLs and that would seem a more common problem. But if
it's a problem, it's a problem, and since it's not necessary, it's easier
to not allow.
>
> --
> -- René Ferdinand Rivera Morell
> -- Don't Assume Anything -- No Supone Nada
> -- Robot Dreams - http://robot-dreams.net
>
Received on 2024-10-15 14:48:00