From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam command language
Date: Tue, 7 Oct 2003 19:34:57 +0100 [thread overview]
Message-ID: <69239ed0eda4832cf8644e945d012b7e@vitanuova.com> (raw)
In-Reply-To: <FB002424-F80E-11D7-B395-000A95B984D8@mightycheese.com>
> and then, in the end, i felt the need for the modified version of ^
> and $ so rarely that i don't really mind not having them.
for me, it's been frequent enough to feel a little frustrated by it
(particularly when dealing non-line-oriented files).
i wouldn't modify the meaning of ^ and $, rooted as they are in
antiquity. one could always take a brave leap into the almost
unsullied waters of Unicode...
for instance, one could use « (unicode 0xab) and » (unicode 0xbb) to
indicate a regex anchored to the start or end of "dot".
e.g.
,x/[a-zA-Z0-9]+/g/«A/d
would delete all alphanumeric sequences starting with
the letter 'A'; or
,y/[ \t\n]/y/«./g/./|tr 'A-Z' 'a-z'
would lowercase all but the first letter of all words. (aside: has
anyone found a good use for the fact that "y" selects null ranges?)
or
,x/^\.TS/.,/^\.TE/y/«...\n/y/...»/x/.*\n»/g/pattern/d
would delete the last line of a tbl table if it contained "pattern".
it seems useful and quite natural to use (and the implementation looks
trivial, in acme at any rate).
BTW while on minor sam/acme gripes, is it a bug or a feature that if a
file is written, changed, and the change undone, the file is not
marked as changed? this means that X/'/w is not guaranteed to write
out all files that have been modified from their on-disk copies, and
has bitten me more than once (i don't use that idiom any more!)
next prev parent reply other threads:[~2003-10-07 18:34 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 7:46 [9fans] Newbie: life without rio Tiit Lankots
2003-10-02 7:49 ` Stephen Wynne
2003-10-02 16:39 ` splite
2003-10-02 17:24 ` David Lukes
2003-10-02 21:02 ` boyd, rounin
2003-10-02 21:06 ` David Presotto
2003-10-02 21:11 ` boydomatic
2003-10-02 21:22 ` boyd, rounin
2003-10-03 1:18 ` boyd, rounin
2003-10-02 21:20 ` boyd, rounin
2003-10-02 18:13 ` jmk
2003-10-02 18:19 ` ron minnich
2003-10-02 21:13 ` boyd, rounin
2003-10-03 8:44 ` kim kubik
2003-10-03 9:04 ` boyd
2003-10-03 13:38 ` andrey mirtchovski
2003-10-03 13:39 ` david presotto
2003-10-03 13:49 ` david presotto
2003-10-03 16:32 ` Dan Cross
2003-10-03 16:34 ` Dan Cross
2003-10-03 16:34 ` David Presotto
2003-10-03 16:42 ` ron minnich
2003-10-06 9:01 ` kim kubik
2003-10-06 9:32 ` boyd
2003-10-03 17:10 ` Skip Tavakkolian
2003-10-04 8:02 ` boyd
2003-10-04 8:00 ` boyd
2003-10-04 7:57 ` boyd
2003-10-02 20:37 ` boyd
2003-10-02 21:11 ` boyd, rounin
2003-10-06 8:08 ` vdharani
2003-10-02 7:52 ` boyd, rounin
2003-10-03 17:36 ` a
2003-10-03 17:47 ` rog
2003-10-04 1:53 ` rob pike, esq.
2003-10-04 8:17 ` boyd
2003-10-06 12:52 ` [9fans] sam command language rog
2003-10-06 15:08 ` Rob Pike
2003-10-06 15:55 ` Jim Choate
2003-10-06 16:35 ` Micah Stetson
2003-10-06 16:41 ` Rob Pike
2003-10-06 16:47 ` Micah Stetson
2003-10-06 18:24 ` boyd
2003-10-07 18:34 ` rog [this message]
2003-10-07 18:48 ` rob pike, esq.
2003-10-08 14:44 ` rog
2003-10-08 15:09 ` Jim Choate
2003-10-09 0:52 ` okamoto
2003-10-08 15:46 ` rob pike, esq.
2003-10-09 17:35 ` rog
2003-10-07 20:16 ` vdharani
2003-10-07 18:59 ` Russ Cox
2003-10-08 14:33 ` rog
2003-10-08 14:44 ` Derek Fawcus
2003-10-08 15:27 ` Dan Cross
2003-10-04 8:14 ` [9fans] Newbie: life without rio boyd
2003-10-04 8:06 ` boyd
2003-10-07 8:58 [9fans] sam command language steve.simon
2003-10-07 9:38 ` Axel Belinfante
2003-10-07 19:16 Scott Schwartz
2003-10-07 19:20 ` rob pike, esq.
2003-10-08 8:37 ` Douglas A. Gwyn
2003-10-08 15:42 ` rob pike, esq.
2003-10-09 8:42 ` Douglas A. Gwyn
2003-10-09 9:18 ` Richard Miller
2003-10-09 15:01 ` rog
2003-10-10 0:26 Dennis Ritchie
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=69239ed0eda4832cf8644e945d012b7e@vitanuova.com \
--to=rog@vitanuova.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).