From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rc file name matching
Date: Wed, 16 Feb 2011 16:28:36 +0100 [thread overview]
Message-ID: <AANLkTin6p0nqsyeFqeLs9y=s5zy69ptHKHqO-Dp38HJ8@mail.gmail.com> (raw)
In-Reply-To: <6DE0DC6E-B495-45A1-ABCE-3CB5BC238D6F@9srv.net>
I am not restricted to rc only. I was doing something similar to you,
but then it occurred to me that perhaps there was an easy way to do it
with rc; apparently there isn't ☺
2011/2/16 Anthony Sorace <a@9srv.net>:
> I hadn't thought of erik's answer. I usually end up doing something
> like "cat `{ls | grep -v hola}" or the like. I find that easier to read,
> unless you're really restricted to literally using just rc for some reason.
>
>
--
Hugo
prev parent reply other threads:[~2011-02-16 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 14:56 hugo rivera
2011-02-16 15:08 ` erik quanstrom
2011-02-16 15:18 ` hugo rivera
2011-02-16 15:15 ` Anthony Sorace
2011-02-16 15:28 ` 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='AANLkTin6p0nqsyeFqeLs9y=s5zy69ptHKHqO-Dp38HJ8@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).