From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] command repetition in sam/acme
Date: Wed, 4 Mar 2009 09:37:31 -0500 [thread overview]
Message-ID: <3ec2e3c33c26f69a1ac8fa3c807997f4@quanstro.net> (raw)
In-Reply-To: <a560a5d00903040614j12be4617g8870f2c4710e3010@mail.gmail.com>
> The result of this discussion basically has been: neither acme nor sam
> is suited for the original problem, there is no simple way present in
> plan9 allowing you to edit such files with long lines, which are quite
> commonly and with justification present in the world. Only Vim, which
> was ported to plan9, with its regexps, can do it gracefully. Thus if
> you want to edit a file, you are forced to use bloated regexps present
> in Vim. Isn't it sad being in plan9?! Things should be simple, but not
> simpler than that.
i disagree with your premise that only vim has the vigor to
modify your super special file. all you need is f and f*.
f transforms your source into something easy to edit in acme.
f* transforms it back into the original form. easy peasy.
or, you can write a simple program that edits the file
directly. there are so many ways to do this, and i'm just
too lazy to list them all.
- erik
next prev parent reply other threads:[~2009-03-04 14:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 12:07 Rudolf Sykora
2009-03-03 12:49 ` Steve Simon
2009-03-03 13:53 ` Rudolf Sykora
2009-03-03 15:40 ` roger peppe
2009-03-03 15:58 ` yy
2009-03-03 16:25 ` Rudolf Sykora
2009-03-03 15:58 ` Uriel
2009-03-03 15:59 ` Uriel
2009-03-03 14:15 ` John Stalker
2009-03-03 14:23 ` Rudolf Sykora
2009-03-03 16:09 ` Russ Cox
2009-03-03 16:31 ` roger peppe
2009-03-03 17:16 ` Uriel
2009-03-03 18:50 ` Rudolf Sykora
2009-03-03 16:39 ` Rudolf Sykora
2009-03-03 20:30 ` Arvindh Rajesh Tamilmani
2009-03-03 22:13 ` ron minnich
2009-03-03 23:19 ` J.R. Mauro
2009-03-03 23:37 ` Anthony Sorace
2009-03-04 0:31 ` Rob Pike
2009-03-04 0:44 ` J.R. Mauro
2009-03-04 0:56 ` Rob Pike
2009-03-04 1:51 ` J.R. Mauro
2009-03-04 2:15 ` Rob Pike
2009-03-04 4:59 ` J.R. Mauro
2009-03-04 9:41 ` Rudolf Sykora
2009-03-04 9:52 ` Rob Pike
2009-03-04 11:32 ` Rudolf Sykora
2009-03-04 13:31 ` Uriel
2009-03-04 13:41 ` Rudolf Sykora
2009-03-04 16:35 ` John Stalker
2009-03-04 16:56 ` ron minnich
2009-03-04 13:37 ` erik quanstrom
2009-03-04 14:14 ` Rudolf Sykora
2009-03-04 14:37 ` erik quanstrom [this message]
2009-03-04 14:59 ` Rudolf Sykora
2009-03-04 16:34 ` Steve Simon
2009-03-04 17:03 ` Russ Cox
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=3ec2e3c33c26f69a1ac8fa3c807997f4@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).