9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] regular expressions in plan9 different from the ones in unix? (at least linux)
Date: Fri, 23 Feb 2007 08:02:13 -0500	[thread overview]
Message-ID: <2fed0cd7578acdab872e594bac7911fb@coraid.com> (raw)
In-Reply-To: <599f06db0702230417r18697174k606712cddd41e6b9@mail.gmail.com>

i don't think that sort of absolutist thinking really works.
i used gnu grep (and all the other gnu tools) on utf-8 stuff 
from the time of the first sam release for unix till i stopped using 
linux for much development.  i never had a problem with
g(ed|sed|awk|e?grep) tripping on utf-8 when the local was
unset or "C".  i did keep in mind that . wasn't going to match
"☺", though.

we all know the limitations of our tools.  that doesn't make
them broken.  

just because plan 9 does bad things if you exceed NPROCS,
doesn't make it broken.

- erik

On 2/23/07, erik quanstrom <quanstro@coraid.com> wrote:
>         ; egrep '[��]0' fu
>         ; egrep '^.0' fu
>


      reply	other threads:[~2007-02-23 13:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 22:16 Folkert van Heusden
2007-02-22 23:17 ` Alberto Cortés
2007-02-22 23:21 ` William Josephson
2007-02-22 23:48   ` Russ Cox
2007-02-23  6:27     ` Composition of regexps (Was re: [9fans] regular expressions in plan9 different from the ones in unix?) Joel Salomon
2007-02-23  6:54       ` William K. Josephson
2007-02-23 13:34         ` Joel C. Salomon
2007-02-23 17:33       ` Russ Cox
2007-02-23 11:19     ` [9fans] regular expressions in plan9 different from the ones in unix? (at least linux) Gorka Guardiola
2007-02-23 12:12       ` erik quanstrom
2007-02-23 12:17         ` Gorka Guardiola
2007-02-23 13:02           ` erik quanstrom [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=2fed0cd7578acdab872e594bac7911fb@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).