From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Borderless rio
Date: Mon, 27 Apr 2009 07:39:19 -0400 [thread overview]
Message-ID: <5d2d5dcc9e187b8745b2b269b103dbc5@quanstro.net> (raw)
In-Reply-To: <a81fe9be0904261130k551347eg62e51a8236249466@mail.gmail.com>
> labels=$*
> if(test $#labels -lt 1)
> labels=(1 2 3 4)
>
> rio.b -I -i'\
> for(label in $labels)
> window -miny 40 ''rio -i ''''label ''$label''''''''
> # give time to set all the labels
> sleep 0.5
> window -dy 39 ''winwatch -e ''''^(winwatch|stats|faces)'''''''
>
> My question is: what is the better way to avoid that lot of quotes? I
> can think of variables or functions, but I wonder what is the idiom
> for nested quotes.
you could use here documents, but i don't really think that would be
better.
it's interesting that duff's shell does fall into the same quoting pit as
bourne's, just in more esoteric situations.
- erik
next prev parent reply other threads:[~2009-04-27 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 18:30 yy
2009-04-27 11:39 ` erik quanstrom [this message]
2009-04-28 22:48 ` Russ Cox
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=5d2d5dcc9e187b8745b2b269b103dbc5@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).