9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: 9p-st@imu.li
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Octets regexp
Date: Thu,  2 May 2013 16:17:11 -0400	[thread overview]
Message-ID: <257b5f.5863bd23.PHUY.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <20130502193952.GA662@polynum.com>

> On Thu, May 02, 2013 at 03:22:21PM -0400, erik quanstrom wrote:
> > can you give an example of xd outputting something that's not a rune?

if we're talking about xd, i'll suggest 'tcs -f 8859-1' again in which case:

> Indeed, if the regexp is an ASCII representation matching xd outputs
> there is not _this_ problem. But this is limited regexp, since one can
> not use "character" ranges (it depends on the size); not '.';

these problems go away

> because the conversion has to be done;

this remains

> because there is still the newline problem (that is added; not something in
> the original data) (if functions have been added to not deal with the
> newline, it is because the newline is a problem, and because regexp have a
> more wider use than "text").

and this problem goes away.

i imagine you'll still have problems with embedded NULs, but that's C
strings for you...

if you want a library function, use rregexec(2) and rregsub(2) with only
the low byte of each Rune filled...

(and yes, your data does quadruple itself)

tristan

-- 
All original matter is hereby placed immediately under the public domain.



  parent reply	other threads:[~2013-05-02 20:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 12:38 tlaronde
2013-05-02 12:48 ` erik quanstrom
2013-05-02 13:25   ` tlaronde
2013-05-02 13:43     ` Tristan
2013-05-02 14:19       ` Tristan
2013-05-02 14:51       ` tlaronde
2013-05-02 15:02         ` Bence Fábián
2013-05-02 15:20           ` tlaronde
2013-05-02 15:27             ` erik quanstrom
2013-05-02 15:10         ` Kurt H Maier
2013-05-02 15:21           ` tlaronde
2013-05-02 13:44     ` erik quanstrom
2013-05-02 14:43       ` tlaronde
2013-05-02 14:58     ` a
2013-05-02 15:08       ` tlaronde
2013-05-02 15:19         ` erik quanstrom
2013-05-02 15:31           ` tlaronde
2013-05-02 16:53             ` erik quanstrom
2013-05-02 18:59               ` tlaronde
2013-05-02 18:45           ` dexen deVries
2013-05-02 19:04             ` tlaronde
2013-05-02 19:22               ` erik quanstrom
2013-05-02 19:39                 ` tlaronde
2013-05-02 20:13                   ` erik quanstrom
2013-05-02 20:17                   ` 9p-st [this message]
2013-05-03 11:16                     ` tlaronde
2013-05-03 13:15                       ` Tristan
2013-05-03 16:33                         ` tlaronde
2013-05-02 16:16 ` tlaronde

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=257b5f.5863bd23.PHUY.mx@tumtum.plumbweb.net \
    --to=9p-st@imu.li \
    --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).