public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: The Cygwin User Guide on path names
Date: Tue, 23 Aug 2016 16:25:00 -0000	[thread overview]
Message-ID: <6a728c0c-81e8-b92b-8344-476d736e2306@cornell.edu> (raw)

The section on path names in the user guide 
(https://cygwin.com/cygwin-ug-net/using.html#using-pathnames) strikes me 
as misleading when it says in the first sentence, "Cygwin supports both 
POSIX- and Win32-style paths."  I think it would be better to say "The 
Cygwin DLL" and to emphasize that Cygwin applications do *not* 
necessarily support Win32 paths.  See

   https://www.cygwin.com/ml/cygwin/2016-08/msg00409.html

for a recent example where this has come up.  It's also come up in 
connection with git and emacs and probably many other applications.

The documentation also says, "The usage of Win32 paths, though possible, 
is deprecated...."  I wonder if this should be strengthened to say 
something like, "The usage of Win32 paths, though possible, is strongly 
deprecated and may be removed in a future release of Cygwin."

I'll be glad to prepare a documentation patch.

Ken

--
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

             reply	other threads:[~2016-08-23 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 16:25 Ken Brown [this message]
2016-08-23 16:35 ` Corinna Vinschen
2016-08-24 15:02 ` Andrey Repin
2016-08-25 17:54   ` Linda Walsh
2016-08-26  8:05     ` Andrey Repin
2016-08-26 13:08       ` Mark Hansen
2016-08-26 13:19         ` Andrey Repin
2016-08-29  2:07           ` Linda Walsh
2016-08-29 11:00             ` Mark Hansen
2016-08-29 11:15               ` Mark Hansen
2016-08-29 16:10             ` Andrey Repin
2016-08-26 13:50         ` Mark Hansen

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=6a728c0c-81e8-b92b-8344-476d736e2306@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).