From: 9p-st@imu.li (Tristan Plumb)
Subject: [9fans] Making read(1) an rc(1) builtin?
Date: Mon, 4 Apr 2011 03:54:44 -0400 [thread overview]
Message-ID: <257867.d17c021e.pp6m.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net>
(right, sorry erik for the double)
> i hate to be pedantic,
By all means, please be pedantic, I was flat wrong.
>ifs is not a list; it is a set of characters like strpbrk(2).
And it matches [$ifs]+ which is the other piece I always forget.
> for(line in `{ifs=$nl cat}){...}
That is exactly what I was saying, thank you. That's what I get for
spending the last few days writing in php, sigh.
> as per plan 9 tradition, the first non-option terminates
> option processing. lindon's echon is not required. giving
> echo -n as its first argument works fine.
What I thought smiley was referring to is when the first argument is
inteded to output -n, but doesn't. What I gave obviously puts an extra
space in (I guess I was a bit fuzzy earlier), echo -n $it^$nl works if
$it is not a list. I've never seen this be a problem in practice myself.
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2011-04-04 7:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 22:30 smiley at zenzebra.mv.com
2011-04-03 23:22 ` pmarin
2011-04-03 23:41 ` Tristan Plumb
2011-04-04 2:02 ` Ethan Grammatikidis
2011-04-04 2:53 ` erik quanstrom
2011-04-04 7:54 ` Tristan Plumb [this message]
2011-04-04 9:26 ` roger peppe
2011-04-04 21:35 ` smiley
2011-04-04 21:46 ` Anthony Sorace
2011-04-04 22:03 ` erik quanstrom
2011-04-05 8:57 ` Balwinder S Dheeman
2011-04-04 22:00 ` Oleg Finkelshteyn
2011-04-04 22:33 ` erik quanstrom
2011-04-04 23:01 ` Lyndon Nerenberg
2011-04-05 8:58 ` yy
2011-04-05 19:54 ` Ethan Grammatikidis
2011-04-05 19:56 ` erik quanstrom
2011-04-05 20:54 ` Ethan Grammatikidis
2011-04-05 21:53 ` andrey mirtchovski
2011-04-06 16:32 ` Bakul Shah
2011-04-06 16:43 ` roger peppe
2011-04-06 18:15 ` erik quanstrom
2011-04-06 18:37 ` Yaroslav
2011-04-07 8:45 ` Greg Comeau
2011-04-06 18:18 ` erik quanstrom
2011-04-07 8:45 ` Greg Comeau
2011-04-05 9:10 ` roger peppe
2011-04-05 15:47 ` ron minnich
2011-04-05 15:52 ` Jacob Todd
2011-04-05 15:57 ` erik quanstrom
2011-04-05 16:04 ` Rudolf Sykora
2011-04-05 17:17 ` ron minnich
2011-04-05 17:49 ` smiley
2011-04-05 18:01 ` erik quanstrom
2011-04-05 19:50 ` Yaroslav
2011-04-06 15:27 ` smiley
2011-04-06 15:32 ` Jacob Todd
2011-04-07 1:26 ` [9fans] Busy mouse WAS: " smiley
2011-04-07 11:49 ` erik quanstrom
2011-04-07 19:59 ` smiley
2011-04-07 20:19 ` erik quanstrom
2011-04-09 12:26 ` smiley
2011-04-09 12:33 ` erik quanstrom
2011-04-05 16:28 ` [9fans] " dexen deVries
2011-04-05 17:05 ` Bakul Shah
2011-04-03 23:51 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-04-04 3:01 ` 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=257867.d17c021e.pp6m.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
/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).