From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: spaces in filenames should be a crime.
Date: Mon, 27 Mar 2017 20:53:17 +0200 [thread overview]
Message-ID: <CABZhJg8AP8gkLeMfjv+OLNEMh97WMzhxrZ_UfgNUayf1DjmyjQ@mail.gmail.com> (raw)
In-Reply-To: <85ef8db4-4fda-8276-3058-ab319ccb68bc@eastlink.ca>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
If you'd suggest a solution using 'ls' on the bash-help mailing list, you'd
get lynched. Although I have always found the tone on that list less than
welcoming, I've taken that recommendation to heart. What is the opinion
here? Should 'ls' as a basis for file name generation be avoided at all
cost? It's pretty clear that it is never a necessary tool for the job.
next prev parent reply other threads:[~2017-03-27 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 20:22 Ray Andrews
2017-03-26 20:57 ` Vadim A. Misbakh-Soloviov
2017-03-26 21:18 ` Daniel Shahaf
2017-03-26 22:41 ` Ray Andrews
2017-03-26 23:20 ` Bart Schaefer
2017-03-27 0:47 ` Ray Andrews
2017-03-27 1:11 ` Chris ccb
2017-03-27 1:45 ` Ray Andrews
2017-03-27 1:44 ` Martijn Dekker
2017-03-27 2:17 ` Ray Andrews
2017-03-27 18:53 ` Jesper Nygårds [this message]
2017-03-27 23:18 ` Mikael Magnusson
2017-03-28 0:46 ` Ray Andrews
2017-03-28 9:08 ` Martin Richter
2017-03-28 14:29 ` Ray Andrews
2017-03-28 16:10 ` Daniel Shahaf
2017-03-28 18:01 ` Ray Andrews
2017-03-28 18:38 ` Martijn Dekker
[not found] ` <60a213ad-6cb3-bef4-9e61-f2c1611a5e71__30788.3357666016$1490694707$gmane$org@gmx.de>
2017-03-29 11:27 ` Stephane Chazelas
2017-03-29 14:50 ` Ray Andrews
2017-03-29 15:21 ` Peter Stephenson
2017-03-29 16:21 ` Ray Andrews
2017-03-30 17:36 ` Bart Schaefer
2017-03-28 16:42 ` Matthew Martin
2017-03-26 21:24 ` Peter Stephenson
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=CABZhJg8AP8gkLeMfjv+OLNEMh97WMzhxrZ_UfgNUayf1DjmyjQ@mail.gmail.com \
--to=jesper.nygards@gmail.com \
--cc=zsh-users@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).