From: incog <incog@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: SegFault running "ls -l" after Microsoft Patch Day
Date: Sun, 20 Dec 2015 11:50:00 -0000 [thread overview]
Message-ID: <00a1ad6ccca67af73db1596ff3f7e9f1@xs4all.nl> (raw)
In-Reply-To: <567693DC.1090507@dwalin.fsnet.co.uk>
On 2015-12-20 12:41, Sam Edge wrote:
> On 18/12/2015 13:06, Dr Rainer Woitok wrote:
>> and (of all things!) contain blanks,
>
> * rant mode on *
>
> What's wrong with blanks?
>
> The OS calls don't give a monkey's chuff so long as they're given
> null-terminated C-strings. Tools like find, xargs etc. have options to
> cope.
>
> The biggest problem is that there are a lot of sloppily written shell
> scripts out there that don't properly quote substitutions or that use
> $*
> instead of "$@" or that use command substitution where they should be
> using pipes and "xargs" and "read". That's the fault of the scripts,
> not
> the OS/emulation layer.
>
> * rant mode off *
Oh ... you know, I understand Rainer's sentiment ...
https://www.cygwin.com/ starts with:
CYGWIN
Get that ___Linux___ feeling - on Windows
...
Regards,
Henri
--
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
next prev parent reply other threads:[~2015-12-20 11:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 13:05 Dr Rainer Woitok
2015-12-14 14:05 ` Corinna Vinschen
2015-12-15 19:29 ` Dr Rainer Woitok
2015-12-16 16:48 ` Corinna Vinschen
2015-12-19 17:08 ` Dr Rainer Woitok
2015-12-20 11:41 ` Sam Edge
2015-12-20 11:50 ` incog [this message]
2015-12-20 12:19 ` Corinna Vinschen
2015-12-20 12:55 ` Houder
2015-12-20 13:20 ` Corinna Vinschen
2015-12-20 13:31 ` Houder
2015-12-20 17:23 ` Sam Edge
2015-12-21 12:43 ` Corinna Vinschen
2015-12-30 18:12 ` Dr Rainer Woitok
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=00a1ad6ccca67af73db1596ff3f7e9f1@xs4all.nl \
--to=incog@xs4all.nl \
--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).