DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; q=dns; s=default; b=KjM
	tP1zUDDWRD1AR4FCS6roTIoR9A8SQoxikWqlLJ+5gYaFJVJrFpEufCFQjc9xeINo
	JtoRuB+y5dfMx0uYjEAKtuqnupAPNUQGF014e7aqVjTm+JRoDq76OA0urf5KYqMH
	NEUkbzRpEymaVUsSND9TT8/Cqf8SYJhVBQt4gwdw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 16 Mar 2018 08:05:53 -0500
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: // is Very Useful
Mime-Version: 1.0
Message-ID: <863wcPNe26176S01.1521205553@web01.cms.usa.net>
Content-Type: text/plain; charset=ISO-8859-1
Z-USANET-MsgId: XID554wcPNF28032X34
Content-Transfer-Encoding: 8bit


Amid all this channel noise about Cygwin vs. Linux/POSIX handling of leading
// in pathnames,
I gotta point out that the Cygwin handling is _hugely_ pragmatic and useful.

It extends the Windows UNC filename notion into a ?nixy network filesystem
namespace in the natural and obvious way.  It puts the corresponding behavior
of the native Windows tools like cmd.exe and "explorer" to shame.  I type the
construct dozens of times per day at the bash prompt; I have aliases, scripts
and tricks ad infinatum that depend on the syntax.

In fact, I believe I have seen some chatter in the true-Linux world about
adopting or adapting the syntax for similar purposes.  Which I find a cheerful
thought: the ardent ancient warriors on both sides are becoming more pragmatic
in their old age.  As am I...


---
Karl Botts, kdbotts@usa.net


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