public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Nicholas Clark <nicholas.clark@gmail.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
Date: Thu, 06 Aug 2015 11:35:00 -0000	[thread overview]
Message-ID: <501181462.20150806143035@yandex.ru> (raw)
In-Reply-To: <CAKNeuBqASXv_LC0vJC3F9bVDauQJ-1tWTT5L+to4JbGejyaXrw@mail.gmail.com>

Greetings, Nicholas Clark!

> You're certainly right that there are nicer ways to write that script.
> My point with the sample script above is that I'm currently using a
> Windows-style HOME path, and it works fine.

If it would stop working, you'll have to o and revisit your mess to pull the
cruft out of the pipes.

> Chances are there are a bunch of other users out there who also use a
> Windows-style HOME path in messy .bat files - I just wanted to
> illuminate that making Windows paths illegal is likely to break a
> whole bunch of users' scripts, and really offers no benefit.

Chances are, they can go and revisit their mess once in a lifetime.
When 1.7.35 came out, I went and dug up every corner of my system to make sure
I no longer have the need for wrappers like yours.

Recently I started to write portable scripts for my private project and I've
replaced Cygwin's /bin/sh (which is in fact bash) with a symlink to /bin/dash.
We'll see how far I can go with it. Already found a number of scripts that
break under strict POSIX shell. None of them Cygwin scripts. Yet.


-- 
With best regards,
Andrey Repin
Thursday, August 6, 2015 14:26:24

Sorry for my terrible english...


--
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:[~2015-08-06 11:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 13:28 Corinna Vinschen
2015-08-03 18:43 ` Thomas Wolff
2015-08-03 19:29   ` Corinna Vinschen
2015-08-04  7:51     ` Achim Gratz
2015-08-04 18:14       ` Warren Young
2015-08-04 18:44         ` Thomas Wolff
2015-08-04 18:53         ` Achim Gratz
2015-08-05  7:54           ` Corinna Vinschen
2015-08-05  9:09             ` Thomas Wolff
2015-08-05 10:12               ` Corinna Vinschen
2015-08-06 12:03                 ` Thomas Wolff
2015-08-07  9:04                   ` Corinna Vinschen
2015-08-07 15:27                     ` cyg Simple
2015-08-07 22:19                     ` Thomas Wolff
2015-08-05  9:19             ` Kiehl, Horst
2015-08-05 10:09               ` Corinna Vinschen
2015-08-05 16:50               ` Andrey Repin
2015-08-05 16:50             ` Andrey Repin
2015-08-05 23:58               ` Nicholas Clark
2015-08-06  0:20                 ` Andrey Repin
2015-08-06  0:35                   ` Nicholas Clark
2015-08-06 11:35                     ` Andrey Repin [this message]
2015-08-07 15:16             ` cyg Simple

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=501181462.20150806143035@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=nicholas.clark@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).