9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Joining multicolumn files
Date: Thu,  2 Jul 2009 17:29:40 +0200	[thread overview]
Message-ID: <138575260907020829h658bdbd6h301de67fa84a75bc@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0907020811q77002f1amf87068d97830522f@mail.gmail.com>

Thanks Russ.
I have tryed it yet, but now I know where to start from.

2009/7/2, Russ Cox <rsc@swtch.com>:
> #!/bin/rc
>  awk 'BEGIN{
>         for(;;){
>                 $0="";
>                 ok=getline<ARGV[1];
>                 x=$0;
>                 if(!(getline<ARGV[2]) && !ok)
>                         break;
>                 print x " " $0
>         }
>  }' $1 $2
>
>
>  Russ
>
>


--
Hugo



      reply	other threads:[~2009-07-02 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 14:54 hugo rivera
2009-07-02 15:11 ` Russ Cox
2009-07-02 15:29   ` hugo rivera [this message]

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=138575260907020829h658bdbd6h301de67fa84a75bc@mail.gmail.com \
    --to=uair00@gmail.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).