From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Octets regexp
Date: Thu, 2 May 2013 12:53:19 -0400 [thread overview]
Message-ID: <b774f33e1a1610f493d3e1290664dd62@ladd.quanstro.net> (raw)
In-Reply-To: <20130502153131.GA1460@polynum.com>
> > is your proposal
> > - to change programs that take regular expressions to be exceptions to
> > the plan 9 text model, or
>
> No: to have a libregexp being agnostic about any encoding. The tools can
> stay, for user, the same, simply libregexp would not be "text" based but
> octets based.
there's always an encoding.
> > - to change the plan 9 text model
>
> Neither. The "text" model is a user interface. My question is simply how
> is it difficult to have an alternative, special purpose, user interface,
> that do not have the UTF-8 filter for input from and output to the user
> interface.
i see we're at an impass. since i don't agree that utf-8 is a user
interface thing. it's more entrenched than that.
why don't you code something up?
- erik
next prev parent reply other threads:[~2013-05-02 16:53 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 [this message]
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
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=b774f33e1a1610f493d3e1290664dd62@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).