From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sed question (OT)
Date: Fri, 30 Oct 2009 13:35:32 +0000 [thread overview]
Message-ID: <DB8E1D59AFC400A9070B1E15@[192.168.1.2]> (raw)
In-Reply-To: <f631016df731e553421e6079dd1da0d4@quintile.net>
Listing of file 'sedscr:'
> s/^/ /;
> s/$/aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ/;
> s/ \([a-z]\)\(.*\1\)\(.\)/ \3\2\3/;
> s/ \([a-z]\)\(.*\1\)\(.\)/ \3\2\3/;
> s/.\{52\}$//;
> s/ //;
$ echo This is a test | sed -f sedscr
This Is a test
$ echo someone forgot to capitalize | sed -f sedscr
Someone Forgot to capitalize
This works with '/usr/bin/sed' from a FreeBSD 6.2-RELEASE installation.
Above sed script stolen from:
<http://dervish.wsisiz.edu.pl/~bse26236/batutil/help/sed/CAPITALI.HTM>
With a minor change: first three words to first two words.
--On Thursday, October 29, 2009 15:41 +0000 Steve Simon
<steve@quintile.net> wrote:
> Sorry, not really the place for such questions but...
>
> I always struggle with sed, awk is easy but sed makes my head hurt.
>
> I am trying to capitalise the first tow words on each line (I could use
> awk as well but I have to use sed so it seems churlish to start another
> process).
>
> capitalising the first word on the line is easy enough:
>
> h
> s/^(.).*/\1/
> y/abcdefghijklmnopqrstuvwxyz/ABCDEFGHIJKLMNOPQRSTUVWXYZ/
> x
> s/^.(.*)/\1/
> x
> G
> s/\n//
>
> Though there maye be a much easier/more elegant way to do this,
> but for the 2nd word it gets much harder.
>
> What I really want is sam's ability to select a letter and operate on it
> rather than everything being line based as sed seems to be.
>
> any neat solutions? (extra points awarded for use of the branch operator
> :-)
>
> -Steve
>
next prev parent reply other threads:[~2009-10-30 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 15:41 Steve Simon
2009-10-29 16:06 ` Lorenzo Bolla
2009-10-29 16:33 ` Iruata Souza
2009-10-29 16:42 ` Lorenzo Bolla
2009-10-29 16:09 ` W B Hacker
2009-10-29 18:52 ` Jason Catena
2009-10-30 13:35 ` Eris Discordia [this message]
2009-10-30 13:39 ` Eris Discordia
2009-10-30 17:30 ` W B Hacker
2009-10-30 17:39 ` [9fans] sed question (OT) (OT) (OT) Tim Newsham
2009-10-30 18:14 ` [9fans] sed question (OT) (OT) (OT) (OT) (OT)(OT)(OT)(OT)(OT)(OT)(OT)(OT)(OT)(OT) W B Hacker
2009-10-30 15:29 ` [9fans] sed question (OT) dave.l
2009-10-30 20:53 ` Noah Evans
2009-11-11 12:32 ` frankg
[not found] <<80c99e790910290906t36766978kcd38c9583392e038@mail.gmail.com>
2009-10-29 16:08 ` erik quanstrom
2009-10-29 16:29 ` Iruata Souza
[not found] <<d1c554290910290929p3980a256hf075042ca3a3917b@mail.gmail.com>
2009-10-29 16:31 ` erik quanstrom
[not found] <<A3AADD7F-E09D-49F9-8A5B-3D6B720046A4@mac.com>
2009-10-30 16:16 ` erik quanstrom
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='DB8E1D59AFC400A9070B1E15@[192.168.1.2]' \
--to=eris.discordia@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).