From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Script to apply Edit commands in acme
Date: Wed, 18 Jan 2023 08:54:49 -0800 [thread overview]
Message-ID: <CA+POUVi=ck-kFhUQEmNn4qo48WV2BkiqijV3OrykO1pmP8C+Hg@mail.gmail.com> (raw)
In-Reply-To: <CALiXCOmZ6k01ixixUxD=AqA=DT_V8MgG4Kvfve5_RDvWD53udg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
You can, of course, execute multiple commands in one Edit, either lineline
or chroding the "{}" block:
Edit {
,x/a/c/b/
,x/d/c/e/
}
On Wed, Jan 18, 2023 at 8:46 AM Henri Ducrocq <henri.ducrocq@gmail.com>
wrote:
> Here is a script I wrote to run any arbitrary command (Edit, Look, etc)
> in a window (current one by default):
> https://gist.github.com/perpen/9902359ddf09b24129277ce121e3e86d
>
> E.g.: Aexe 'Edit ,blah'
>
> It's quite horrible, as it appends the command to the body to run it
> using an event (would have been simpler running the command from the
> tag, but there is race making that impossible iirc).
>
> I ended up not using it, so it is not much tested. And I wrote it for
> plan 9, not
> sure how that would work with plan9port.
>
> On Mon, Jan 16, 2023 at 9:06 AM <revrari@mweb.co.za> wrote:
> >
> > Great tips. Thank you. I had no idea I could run ed commands that way.
> > 9fans / 9fans / see discussions + participants + delivery options
> Permalink
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Taf408751bc6fb344-Mfc6d82c231782e86759f2c05
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2756 bytes --]
next prev parent reply other threads:[~2023-01-18 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 3:49 revrari
2023-01-16 8:17 ` sirjofri
2023-01-16 9:06 ` revrari
2023-01-18 16:44 ` Henri Ducrocq
2023-01-18 16:54 ` Paul Lalonde [this message]
2023-01-19 9:33 ` revrari
2023-01-20 5:25 ` Ben Hancock
2023-01-20 7:23 ` igor
2023-01-20 14:24 ` Ben Hancock
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='CA+POUVi=ck-kFhUQEmNn4qo48WV2BkiqijV3OrykO1pmP8C+Hg@mail.gmail.com' \
--to=paul.a.lalonde@gmail.com \
--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).