public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Bravery, Gavin S" <gavin.bravery@imperial.ac.uk>
To: Chris Sutcliffe <ir0nh34d@gmail.com>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: Slight issue in base-files-4.0-6
Date: Fri, 25 Mar 2011 13:02:00 -0000	[thread overview]
Message-ID: <C5101A1534B7D7418DE06BC355FD7D63160F3D88@icexch-m1.ic.ac.uk> (raw)
In-Reply-To: <AANLkTi=1F1PuDzRjNWSrvk277h=Pv53aAs8V5cU5iBwe@mail.gmail.com>

>> We'd need mksh to network shares for homes first though.
>> My home is: //<servername>/gbravery and it really doesn't like it.
>The newly released mksh-39c-3 handles UNC paths correctly now.

Now that's much better! My #! stuff works and it copes with my home being a UNC perfectly.
I've removed my home-spun pdksh (which included old Debian fixes) and moved over.
Thanks very much Chris for the rapid response, much appreciated.

Gavin

--
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:[~2011-03-25  9:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 14:10 Bravery, Gavin S
2011-03-22 14:47 ` David Sastre
2011-03-22 14:59   ` Chris Sutcliffe
2011-03-22 16:13     ` Bravery, Gavin S
2011-03-22 16:58       ` David Sastre
2011-03-22 16:59         ` Bravery, Gavin S
2011-03-24 15:08           ` Chris Sutcliffe
2011-03-25 13:02             ` Bravery, Gavin S [this message]
2011-03-22 17:39         ` Corinna Vinschen
2011-03-22 17:40         ` Chris Sutcliffe
2011-03-22 23:39         ` Drop pdksh? Christopher Faylor
2011-03-23  0:24           ` Christopher Faylor
2011-03-24 17:35           ` Brian Wilson
2011-03-22 18:02       ` Slight issue in base-files-4.0-6 Chris Sutcliffe

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=C5101A1534B7D7418DE06BC355FD7D63160F3D88@icexch-m1.ic.ac.uk \
    --to=gavin.bravery@imperial.ac.uk \
    --cc=cygwin@cygwin.com \
    --cc=ir0nh34d@gmail.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).