From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] rc behavior with rfork
Date: Wed, 16 May 2012 10:35:20 -0400 [thread overview]
Message-ID: <cbba16d79053cc9117b6859f2373235f@coraid.com> (raw)
In-Reply-To: <e28d7aa800bff3aba9feb3cdc96c2819@sp.inri.net>
On Wed May 16 10:33:50 EDT 2012, sl@9front.org wrote:
> The confusing part to me is why >[2] or >[3] or >[4]
> (and so on) captures the stdout of the @{} block.
>
yes, it is confusing. but that's how rc rolls.
- erik
next prev parent reply other threads:[~2012-05-16 14:35 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 10:14 [9fans] Governance question??? IainWS
2012-05-14 10:32 ` Francisco J Ballesteros
2012-05-14 10:35 ` Bruce Ellis
2012-05-14 10:39 ` Charles Forsyth
2012-05-14 10:43 ` Steve Simon
2012-05-14 10:51 ` Richard Miller
2012-05-14 10:55 ` dexen deVries
2012-05-14 11:54 ` IainWS
2012-05-14 13:05 ` Aram Hăvărneanu
2012-05-14 14:24 ` Ethan Grammatikidis
2012-05-14 14:34 ` sl
2012-05-17 14:57 ` Ethan Grammatikidis
2012-05-17 15:38 ` dexen deVries
2012-05-17 15:45 ` Christoph Lohmann
2012-05-17 15:59 ` Kurt H Maier
2012-05-17 17:18 ` Ethan Grammatikidis
2012-05-14 14:00 ` Anthony Sorace
2012-05-14 14:12 ` Christoph Lohmann
2012-05-15 9:23 ` Anthony Martin
2012-05-15 12:19 ` Christoph Lohmann
2012-05-15 12:37 ` Charles Forsyth
2012-05-15 12:42 ` Burton Samograd
2012-05-15 12:52 ` Connor Lane Smith
2012-05-15 13:01 ` dexen deVries
2012-05-15 16:08 ` Anthony Sorace
2012-05-16 1:41 ` cinap_lenrek
2012-05-16 5:21 ` erik quanstrom
2012-05-16 13:04 ` Christoph Lohmann
2012-05-16 13:16 ` Robert Raschke
2012-05-16 13:33 ` Kurt H Maier
2012-05-16 13:49 ` Charles Forsyth
2012-05-16 14:03 ` hiro
2012-05-16 14:06 ` Francisco J Ballesteros
2012-05-16 14:21 ` Dan Cross
2012-05-16 14:30 ` Charles Forsyth
2012-05-16 15:10 ` Richard Miller
2012-05-16 15:53 ` Charles Forsyth
2012-05-16 15:58 ` sl
2012-05-16 16:15 ` hiro
2012-05-16 14:22 ` Charles Forsyth
2012-05-16 14:11 ` Skip Tavakkolian
2012-05-15 12:42 ` Christoph Lohmann
2012-05-15 13:54 ` erik quanstrom
2012-05-15 14:26 ` Charles Forsyth
2012-05-15 18:54 ` Charles Forsyth
2012-05-15 19:05 ` Francisco J Ballesteros
2012-05-15 22:19 ` hiro
2012-05-15 23:29 ` Skip Tavakkolian
2012-05-15 23:31 ` sl
2012-05-16 7:35 ` [9fans] rc behavior with rfork 9
2012-05-16 7:02 ` Gorka Guardiola
2012-05-16 14:05 ` sl
2012-05-16 14:21 ` Charles Forsyth
2012-05-16 14:31 ` sl
2012-05-16 14:35 ` erik quanstrom [this message]
2012-05-16 15:05 ` Kurt H Maier
2012-05-16 15:35 ` cinap_lenrek
2012-05-16 15:44 ` erik quanstrom
2012-05-16 16:04 ` Charles Forsyth
2012-05-16 14:43 ` Charles Forsyth
2012-05-16 14:49 ` sl
2012-05-16 15:03 ` erik quanstrom
2012-05-16 15:37 ` cinap_lenrek
2012-05-16 0:30 ` [9fans] Governance question??? kokamoto
2012-05-16 0:34 ` cinap_lenrek
2012-05-16 0:49 ` andrey mirtchovski
2012-05-16 7:07 ` Gorka Guardiola
2012-05-16 8:25 ` Francisco J Ballesteros
2012-05-16 11:22 ` hiro
2012-05-16 12:48 ` Charles Forsyth
2012-05-17 0:56 ` kokamoto
2012-05-15 12:30 ` Charles Forsyth
2012-05-15 8:42 ` IainWS
2012-05-14 11:30 ` tlaronde
2012-05-14 11:32 ` Bruce Ellis
2012-05-14 11:47 ` Gorka Guardiola
2012-05-14 14:32 ` Balwinder S Dheeman
2012-05-14 14:57 ` erik quanstrom
2012-05-14 15:15 ` tlaronde
2012-05-14 11:21 ` IainWS
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=cbba16d79053cc9117b6859f2373235f@coraid.com \
--to=quanstro@labs.coraid.com \
--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).