From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Expansion order
Date: Tue, 25 Jan 2005 16:54:56 +0000 [thread overview]
Message-ID: <1050125165457.ZM3942@candle.brasslantern.com> (raw)
In-Reply-To: <200501251453.j0PEr3bo024178@news01.csr.com>
On Jan 25, 2:53pm, Peter Stephenson wrote:
} Subject: Re: Expansion order
}
} typeset -xT LS_OPTIONS="-N --color=tty -T 0" ls_options
} alias ls='ls $ls_options'
}
} This allows for whitespace characters in the options as long as you
} manipulate them through the array ls_options.
Doesn't that need to be
typeset -xT LS_OPTIONS="-N --color=tty -T 0" ls_options ' '
?? Otherwise it's splitting on colons, not spaces.
next prev parent reply other threads:[~2005-01-25 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 14:41 Mads Martin Joergensen
2005-01-25 14:53 ` Peter Stephenson
2005-01-25 16:54 ` Bart Schaefer [this message]
2005-01-25 15:03 ` Stephane Chazelas
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=1050125165457.ZM3942@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/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).