ex: parsing seems still broken about nextvi

[kyx0r]

Nextvi does not support this syntax and there are many problems that I see. At the very least try correct syntax. :e +1 | s/\\|/PIPE/ | w file1 | e file2 | 1 | s/\//SLASH/ | wq

…

On Sat, Jul 22, 2023, 16:51 Stefan ***@***.***> wrote: echo 'foo | bar' > file1; echo 'foo/bar' > file2; vi :edit +1 | s/|/PIPE/ | w file1 | e file2 | 1 | s/\//SLASH/ | wq See https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_18_08 — Reply to this email directly, view it on GitHub <#46>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH52FH4NLIOK4I27EK4ZDADXRQ4NRANCNFSM6AAAAAA2UBQT7E> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kyx0r]

Although the ranges in edit command are not supported. So e +1 probably isn't what you need to use, just use 1

…

On Sat, Jul 22, 2023, 17:20 Kyryl Melekhin ***@***.***> wrote: Nextvi does not support this syntax and there are many problems that I see. At the very least try correct syntax. :e +1 | s/\\|/PIPE/ | w file1 | e file2 | 1 | s/\//SLASH/ | wq On Sat, Jul 22, 2023, 16:51 Stefan ***@***.***> wrote: > echo 'foo | bar' > file1; echo 'foo/bar' > file2; > vi > :edit +1 | s/|/PIPE/ | w file1 | e file2 | 1 | s/\//SLASH/ | wq > > See > https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_18_08 > > — > Reply to this email directly, view it on GitHub > <#46>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH52FH4NLIOK4I27EK4ZDADXRQ4NRANCNFSM6AAAAAA2UBQT7E> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[polluks]

My strange result of "1"

-rw-r--r--  1 polluks  wheel  10 23 Jul 05:49 file1
-rw-------  1 polluks  wheel   0 23 Jul 05:49 file1␣
-rw-r--r--  1 polluks  wheel   8 23 Jul 05:49 file2
-rw-------  1 polluks  wheel   0 23 Jul 05:49 file2␣
$ cat -n file?
     1	foo | bar
     1	foo/bar

[kyx0r]

I think you're not reading the file1, replace edit +1 with e file1, also \\| results in | bar, but thats a syntax error in regular expression, probably need 1 more slash, \\\| I can't quite test this right now. I'm pretty sure this is caused by user error.

…

-Kyryl

On Sat, Jul 22, 2023, 23:53 Stefan ***@***.***> wrote: My strange result of "1" -rw-r--r-- 1 polluks wheel 10 23 Jul 05:49 file1 -rw------- 1 polluks wheel 0 23 Jul 05:49 file1 -rw-r--r-- 1 polluks wheel 8 23 Jul 05:49 file2 -rw------- 1 polluks wheel 0 23 Jul 05:49 file2 $ cat -n file? 1 foo | bar 1 foo/bar — Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH52FHZUN6NXUCWVFE6O753XRSN3XANCNFSM6AAAAAA2UBQT7E> . You are receiving this because you commented.Message ID: ***@***.***>

[polluks]

I see, the files are not doppelgangers but have a trailing space!

[kyx0r]

So the correct command would be:
e file1|s/\|/PIPE/ | w! file1| e file2| 1 | s/\//SLASH/|wq

w! is needed here as you give it same argument will error with "file exists"
you can just use w alone, but just for the sake of being use w!.

I don't really expect production commands to have spaces between the bars, they are not necessary and ambiguous since the space would be passed into resulting ex function and its a gamble weather that function will ignore or not ignore the trailing space.

The only thing I may wanna refactor is the | escapes. I don't think its the special casing is necessary anymore, original idea was to reduce number of slashes for most common uses like \| and | but its rather hard to explain how it works. probably just 1 extra slash can make more sense. Only issue is when using commands like vr, it will not correctly auto escape the | characters, which is probably why this rule was made in the first place.

[kyx0r]

You should try/test the new ex | escape syntax I committed, should be more self explanatory now.

e file1|s/\\|/PIPE/ | w! file1| e file2| 1 | s/\//SLASH/|wq

\| for |
\\| for \|
\\\| for \\|

etc...

[polluks]

close...

$ cat -n file?
     1	PIPEfoo | bar
     1	fooSLASHbar

[kyx0r]

Didn't escape the | properly.

…

On Sun, Jul 23, 2023, 15:23 Stefan ***@***.***> wrote: close... $ cat -n file? 1 PIPEfoo | bar 1 fooSLASHbar — Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH52FH5MHS7ECX3WWI2RBETXRV2ZRANCNFSM6AAAAAA2UBQT7E> . You are receiving this because you commented.Message ID: ***@***.***>