public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: SegFault running "ls -l" after Microsoft Patch Day
Date: Sun, 20 Dec 2015 13:20:00 -0000	[thread overview]
Message-ID: <20151220132026.GC4034@calimero.vinschen.de> (raw)
In-Reply-To: <43e70731a9597802c4101612ac7bb1dd@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 2838 bytes --]

On Dec 20 13:55, Houder wrote:
> On 2015-12-20 13:18, Corinna Vinschen wrote:
> >On Dec 20 12:50, incog wrote:
> >>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
> >
> >Dunno about you, but I have lots of files with spaces in them on Linux,
> >especially files connected with GUI stuff, themes, etc.
> 
> :-) Oh dear, must be my age ... I never create files with spaces in them
> ... I like to keep things simple, just like the guys that created Unix.
> 
> (sorry, could not stop myself :-)))

I didn't say I created them myself.  Or in same case I did but didn't
intend to.

E.g., in one desktop environment I created a subdir with entries
pointing to a script "foo" called with a machine name as parameter.
I called the entries "foo machine1", "foo machine2", etc.  Turns out,
those entries were converted to files called "foo machine1.desktop",
"foo machine2.desktop", ...

Lots of documents downloaded from the net have spaces in them, unless
you rename every single one of them, which I can't be bothered.

KDE created a file
~/.kde/share/apps/desktoptheme/Arezzo/widgets/mock przelacznik pulpitow.svg
I don't even know the language.

~/.config/gnome-boxes/sources/QEMU Session
~/.mozilla/firefox/Crash Reports
~/.thunderbird/xyz.default/Mail/Local Folders/Unsent Messages
~/android-sdk-linux_86/SDK Readme.txt
/usr/local/MegaRAID Storage Manager
/usr/share/cmake/Help/generator/Sublime Text 2.rst
/usr/share/doc/python-setuptools/CHANGES (links).txt
/usr/share/doc/stix-fonts/STIX Font License 2010.pdf
/usr/share/doc/verne-backgrounds-single/CC-BY-SA 3.0

Even the git repo has them:

~/src/git/t/t4135/add-with backslash.diff
~/src/git/t/t4135/add-with quote.diff
~/src/git/t/t4135/add-with spaces.diff
~/src/git/t/t4135/add-with tab.diff


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-20 13:20 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
2015-12-20 12:19             ` Corinna Vinschen
2015-12-20 12:55               ` Houder
2015-12-20 13:20                 ` Corinna Vinschen [this message]
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=20151220132026.GC4034@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).