[9fans] Acme, Edit, code and newline

[9fans] Acme, Edit, code and newline

[Daniel Peyrolon]

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

Hi there,

I'm using p9p's acme, and I would like to take a piece of code and change,
for example this:

int main(int argc, char *argv[]) {

For this:

int main(int argc, char *argv[])
{

So, for doing that, I thought about using some regexps and the Edit command.

I would like to work with some generic regexp, so I wrote the following:

Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*$/ s/[ ]*{[ ]*$/\n{/g

By the man, the x command, under sam(1) does execute the command after the
x. Also, we
have to use \n, instead of a real newline.

AFAICT, these two commands work, separatedly. Using the first one prints me
the whole
set of function definitions, and using the s// when selecting the line that
holds something like:

blah blah (blah blah) {

Does indeed change that for:
blah blah (blah blah)
{

But when used together, this command doesn't work. Could please someone
provide
me with some insight on why this doesn't work? Thanks a lot.

(Sorry for the blah)

--
Daniel

[-- Attachment #2: Type: text/html, Size: 1714 bytes --]

Re: [9fans] Acme, Edit, code and newline

[Mark van Atten]

Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g

Mark.

Re: [9fans] Acme, Edit, code and newline

[erik quanstrom]

On Mon Mar 31 11:37:51 EDT 2014, vanattenmark@gmail.com wrote:
> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g

\ before { is not necesary.

- erik

Re: [9fans] Acme, Edit, code and newline

[Mark van Atten]

> \ before { is not necesary.

Don't know how I got that one in there; thanks for catching it!

Mark.

Re: [9fans] Acme, Edit, code and newline

[erik quanstrom]

> > \ before { is not necesary.
>
> Don't know how I got that one in there; thanks for catching it!

it was in the original.

- erik

Re: [9fans] Acme, Edit, code and newline

[Daniel Peyrolon]

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g

So, it was simply a matter of changing "$" for "\n" at the x command!
How come my command didn't work?
It really should work with the "$", shouldn't it?

Or even without the \n or the $, since the regexp already matched until the
'{',
so the substitution should have worked.

Also, thanks for pointing me that the '\' wasn't actually needed.
Many thanks!



2014-03-31 17:36 GMT+02:00 Mark van Atten <vanattenmark@gmail.com>:

> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
>
> Mark.
>
>


--
Daniel

[-- Attachment #2: Type: text/html, Size: 1856 bytes --]

Re: [9fans] Acme, Edit, code and newline

[Ruben Schuller]

Hi,

2014-03-31 17:54 Daniel Peyrolon <tuchalia@gmail.com>:

> > Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
>
> So, it was simply a matter of changing "$" for "\n" at the x command!
> How come my command didn't work?
> It really should work with the "$", shouldn't it?
>
> Or even without the \n or the $, since the regexp already matched
> until the '{',
> so the substitution should have worked.

I'm not really that proficient in acme/sam but, from the sam
manpage:

       $      The null string at the end of the file.

I'd also recommend reading
http://doc.cat-v.org/bell_labs/sam_lang_tutorial/ .
It helped me a lot getting a better undestanding of the command
language.

Take care,
Ruben

Re: [9fans] Acme, Edit, code and newline

[Mark van Atten]

On Mon, Mar 31, 2014 at 5:54 PM, Daniel Peyrolon <tuchalia@gmail.com> wrote:
>> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
>
> So, it was simply a matter of changing "$" for "\n" at the x command!

Yes. (In the version I gave, the replacement of the second $, the one
in the s command, by \n was superfluous.)

> How come my command didn't work?
> It really should work with the "$", shouldn't it?

In the original version, the x command matches up to the end of the
line, but the resulting selection is no longer itself a line; so the
subsequent s command, trying to match various things and then the
empty string at the end of a line ($), does not succeed.

But replacing, in the x command, the $ by \n leaves the result of a
match (now one character longer because it includes the \n) a line, in
which the s command then successfully matches $.

As ever,
Mark.

Re: [9fans] Acme, Edit, code and newline

[Daniel Peyrolon]

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

Hi there everyone,

Many thanks for the explanation, it's much clearer now.


2014-04-01 9:24 GMT+02:00 Mark van Atten <vanattenmark@gmail.com>:

> On Mon, Mar 31, 2014 at 5:54 PM, Daniel Peyrolon <tuchalia@gmail.com>
> wrote:
> >> Edit , x/^[^ ]+[ ]*[^(]*\([^)]*\)[ ]*\{[ ]*\n/ s/[ ]*\{[ ]*\n/\n\{/g
> >
> > So, it was simply a matter of changing "$" for "\n" at the x command!
>
> Yes. (In the version I gave, the replacement of the second $, the one
> in the s command, by \n was superfluous.)
>
> > How come my command didn't work?
> > It really should work with the "$", shouldn't it?
>
> In the original version, the x command matches up to the end of the
> line, but the resulting selection is no longer itself a line; so the
> subsequent s command, trying to match various things and then the
> empty string at the end of a line ($), does not succeed.
>
> But replacing, in the x command, the $ by \n leaves the result of a
> match (now one character longer because it includes the \n) a line, in
> which the s command then successfully matches $.
>
> As ever,
> Mark.
>
>


--
Daniel

[-- Attachment #2: Type: text/html, Size: 1676 bytes --]