From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: zsh-users@sunsite.dk
Subject: "splitting prpblem"
Date: Thu, 11 Aug 2005 05:17:10 +0200 (CEST) [thread overview]
Message-ID: <20050811.051710.59487319.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <237967ef050810155178939027@mail.gmail.com>
HI,
I have a kind of "splitting problem" -- and dont know how to
categorize or name it...
This is it:
I made a script to repack all my *.tar.bz2 files into *.7z file with
the high compression packer p7zip.
P7zip supports a couple of optimizing options to get most of it in
dependance of the used machine (mem etc...).
To not to repeat these options every time on a line where p7zip is
called I put them into a variable:
opt="-t7z -m0=lzma -mx=8 -mfb=64"
Now...
When calling p7zip with
7z a $opt <file> <arc.7z>
p7zip gets confused, because it sees the parameters in $opt as one
monlithic block of text.
Is there a way to say: "Hey zsh,...if you expand this variable,
please let it look like single options..." ?
I dont want to call big brothers of big sisters of the utils family
like sed, ed, cut, grep or whatever for this tiny job...
(...and for what keyword I had to search for in th ezshall docs...I
tried things like "$1", "variable expansion", "split" and such and
found nothing appropiate...)
Keep zshing!
Meino
next prev parent reply other threads:[~2005-08-11 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <deliverable@gmail.com>
2005-08-10 19:18 ` rm nonexisting*; alias with parameters? Deliverable Mail
2005-08-10 20:06 ` Peter Stephenson
2005-08-10 20:31 ` Deliverable Mail
2005-08-10 22:51 ` Mikael Magnusson
2005-08-11 3:17 ` Meino Christian Cramer [this message]
2005-08-11 8:40 ` "splitting prpblem" Michal Politowski
2005-08-11 17:01 ` Meino Christian Cramer
2009-06-16 3:17 ` serverizing a fat process with named pipes Alexy Khrabrov
2009-06-16 20:29 ` Peter Stephenson
2009-06-17 0:47 ` Bart Schaefer
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=20050811.051710.59487319.Meino.Cramer@gmx.de \
--to=meino.cramer@gmx.de \
--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).