From: Kostarev Ilya <uvelichitel@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [acme] Edit command -- More than one argument?
Date: Mon, 27 Oct 2014 20:29:59 +0300 [thread overview]
Message-ID: <etPan.544e8117.30462046.134@uvelichitels-MacBook-Pro.local> (raw)
In-Reply-To: <e3e6653bd981e5b31659668a20fa3606@krabbe.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
At least p9p acme has multiline tags. Personally, I prefer 2-1 chord complicated or frequent stuff onto Edit command
--
Kostarev Ilya
On 27 Oct 2014 at 18:48:10, Ingo Krabbe (ikrabbe.ask@gmail.com) wrote:
but you can't do this on a acme headline. So how would you apply such multiline commands to a range you marked in the buffer?
> Edit {
> s/^/\[/
> s/\:\ /\]/
> }
>
>
> On Mon, Oct 27, 2014 at 8:28 AM, Eduardo Alvarez <astrochelonian@gmail.com>
> wrote:
>
>> Hello, everyone,
>>
>> I'm in the process of learning acme via Russ Cox's p9p port. Recently, I
>> found
>> myself editing some text to use with markdown, and needed to make more
>> than one
>> modification to a list. I wanted to know if it's possible to give the Edit
>> command more than one argument. For example, I found myself needing to
>> replace
>> colons with a close bracket (]), and inserting an open bracket at the
>> beginning
>> of the line. So I did this:
>>
>> Edit s/^/\[/
>> Edit s/\:\ /\]/
>>
>> And I was hoping to combine these into a single line, so, for example:
>>
>> Edit s/^/\[/ s/\:\ /\]/
>> (Not sure if escaping was necessary, but I was playing it safe)
>>
>> Doing exactly what I did above resulted in the error
>>
>> "Edit: newline expected (saw f)"
>>
>> So that's obviously not it. But I'm not sure if it's at all possible.
>>
>> Thank you in advance.
>> --
>> Eduardo Alvarez
>>
>> "Stercus, Stercus, Stercus, moriturus sum"
>> -- Rincewind The Wizzard
>>
[-- Attachment #2: Type: text/html, Size: 2662 bytes --]
next prev parent reply other threads:[~2014-10-27 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 15:28 Eduardo Alvarez
2014-10-27 15:34 ` Rob Pike
2014-10-27 15:46 ` Ingo Krabbe
2014-10-27 17:09 ` Rob Pike
2014-10-27 17:15 ` lucio
2014-10-27 17:33 ` Ingo Krabbe
2014-10-27 17:33 ` Eduardo Alvarez
2014-10-27 17:35 ` Skip Tavakkolian
2014-10-27 17:29 ` Kostarev Ilya [this message]
2014-10-27 16:41 sl
2014-10-27 22:54 ` Rob Pike
2014-10-27 23:39 ` Paul Lalonde
2014-10-28 3:41 ` erik quanstrom
2014-10-28 3:49 ` Paul Lalonde
2014-10-28 22:51 ` erik quanstrom
2014-10-28 23:08 ` Paul Lalonde
2014-10-28 23:47 ` erik quanstrom
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=etPan.544e8117.30462046.134@uvelichitels-MacBook-Pro.local \
--to=uvelichitel@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).