public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin Setup Command-line Arguments - Paths with a Space Incorrectly Parsed
Date: Tue, 15 Nov 2016 07:33:00 -0000	[thread overview]
Message-ID: <85fb010a-4fb5-1455-af6b-32e95048964c@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+Fg1xZFpb5uBbkP4KQxsZUvkjQETY4VjR0Y4k+Oe_D5DE0u9w@mail.gmail.com>

On 2016-11-14 07:43, Gerrit Haase wrote:
> 2016-11-13 23:19 GMT+01:00 OwN-3m-All wrote:
>> I'd like to automate Cygwin installation, but I don't want to rule
>> out the possibility that a path with a space will not be used.
>
> You'll get a warning from Setup: it is strongly recommended, to use a
> root path without spaces.

I'd go further - it is strongly recommended that you use only a subset
of printable ASCII characters to avoid problems with Windows OEM and
NLS code pages, and Cygwin mapping of some characters to UTF-16 user
defined supplementary characters, understood only by Cygwin internals,
for POSIX compatibility.
So disallow names with anything disallowed by Windows:
	"*/:<>?\|
or outside the [!-~] range leaving [!#-)+-.0-9;=@-[\]-{}~]
It would also be sensible to disallow anything interpreted by shells,
including cmd, or programs, to avoid issues:
	!#$%&'();[]`{}
reducing the set to [+-.0-9=@-Z^_a-z~] i.e.
	+,-.=@^_~
plus digits and letters, to maintain interoperability without issues.
Leading -.@~ should be disallowed as they have special meaning, and
trailing ~ is questionable as it is often used for backup files,
removed by cleanup scripts, so you might also want to disallow these.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-11-14 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-13 23:17 OwN-3m-All
2016-11-14 19:23 ` Gerrit Haase
2016-11-15  3:38   ` Gerrit Haase
2016-11-15  7:33   ` Brian Inglis [this message]
2016-11-15  8:24     ` OwN-3m-All
2016-11-15 18:56       ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85fb010a-4fb5-1455-af6b-32e95048964c@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).