From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: array matching: inconsistent behaviour ?
Date: Wed, 09 Jan 2013 07:56:26 -0800 [thread overview]
Message-ID: <130109075626.ZM9484@torch.brasslantern.com> (raw)
In-Reply-To: <CACQNQ9Nk0=CTGacByEZJYsURZViLSksQ5z-2PfJVvW8LgtTP3w@mail.gmail.com>
On Jan 9, 4:03pm, rahul wrote:
}
} I've been using the "print -rC" to print in columns -- saves me from quite
} a bit of programming. However, often the data has spaces in it, or tabs. Of
} course, print will wrap/break on those.
"print" doesn't do any wrapping/wordsplitting internally, so if you are
getting columns broken up on whitespace in the data, it's because of
command-line parsing. Change the way you quote the arguments to print.
next prev parent reply other threads:[~2013-01-09 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 6:30 rahul
2013-01-09 9:35 ` Han Pingtian
2013-01-09 10:23 ` rahul
2013-01-09 9:40 ` Peter Stephenson
2013-01-09 10:33 ` rahul
2013-01-09 15:56 ` Bart Schaefer [this message]
2013-01-09 16:53 ` rahul
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=130109075626.ZM9484@torch.brasslantern.com \
--to=schaefer@brasslantern.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).