9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] awk help; not plan9 matter
Date: Thu, 17 Sep 2009 22:33:40 +0200	[thread overview]
Message-ID: <a560a5d00909171333t467418c6w8e03756dc5808869@mail.gmail.com> (raw)
In-Reply-To: <df49a7370909171034l1f530e16kae9d2b40077e905a@mail.gmail.com>

2009/9/17 roger peppe <rogpeppe@gmail.com>:
> just change the regexp as required.

Ok. I decided (although just for game now) to play a little with the
idea of building the regexp.
Starting from Eric's post I slowly progressed to sth. quite similar to
your post :) :

fn buildre {
       re = 's:^([ 	]*)('
       for(i in `{seq 1 `{hoc -e $1-1}})
               re = $re ^ '[^ 	]+[ 	]+'
       re = $re ^ ')[^ 	]+:\1\2' ^ $2:
}

This works (even takes care about leading spaces) unless I want to use
it for the 1st field. Then the produced regexp (buildre 1 hell)is

s:^([ 	]*)()[^ 	]+:\1\2hell:

and sed says
sed: Command garbled: s:^([ 	]*)()[^ 	]+:\1\2hell:

Apparently it dislikes the empty group, (). Is there any reason?
I tried it in linux, there with

echo '1 28	 	3' | sed 's:^\([ 	]*\)\(\)[^ 	][^ 	]*:\1\2hell:'

and it works as expected...

Thanks
Ruda



  reply	other threads:[~2009-09-17 20:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  8:23 Rudolf Sykora
2009-09-17  8:37 ` matt
2009-09-17  8:52   ` Rudolf Sykora
2009-09-17  9:04 ` matt
2009-09-17  9:12   ` Rudolf Sykora
2009-09-17 10:42     ` Rudolf Sykora
2009-09-17 12:35       ` yy
2009-09-17 12:55         ` Rudolf Sykora
2009-09-17 15:51     ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-17 16:02       ` erik quanstrom
2009-09-17 16:20         ` roger peppe
2009-09-17 16:55         ` Rudolf Sykora
2009-09-17 17:04           ` erik quanstrom
2009-09-17 17:10             ` erik quanstrom
2009-09-17 17:19               ` Rudolf Sykora
2009-09-17 17:34                 ` roger peppe
2009-09-17 20:33                   ` Rudolf Sykora [this message]
2009-09-17 20:46                     ` erik quanstrom
2009-09-17 21:09                       ` Rudolf Sykora
2009-09-17 21:22                         ` Rudolf Sykora
2009-09-17 21:24                         ` erik quanstrom
2009-09-17 14:16 ` Noah Evans
2009-09-17 14:45   ` roger peppe
2009-09-17 17:03   ` Rudolf Sykora

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=a560a5d00909171333t467418c6w8e03756dc5808869@mail.gmail.com \
    --to=rudolf.sykora@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).