> Hi
>
> rameo wrote:
>
> > Many things don't work in gnu awk.
> > p.e. a simple command like
> > %!awk -F "|" {print $1,$2}
> > doesn't work.
>
> it seems Vim generates an incorrect shell command for this. On my Win 7
> system the command looked like
>
> C:\Windows\system32\cmd.exe /c awk -F " <${TEMP}\VIiBCD2.tmp |" "{print $1,$2}" >${TEMP}\VIoBCD3.tmp 2>&1
>
> where ${TEMP} was replaced by the actual temp directory. As you can see
> the path to the temp file that contains the extract from the current
> file is inserted before the pipe symbol that was supposed to be the
> field separator for awk. If a comma is given as field separator, the
> redirection is correctly appended to the command.
>
> Here are my options relevant to shell commands
>
> shell=C:\Windows\system32\cmd.exe
> shellcmdflag=/c
> shellpipe=>%s 2>&1
> shellquote=
> shellredir=>%s 2>&1
> noshellslash
> shelltemp
> shellxquote=
>
> Regards,
> J�rgen
>
> --
> Sometimes I think the surest sign that intelligent life exists elsewhere
> in the universe is that none of it has tried to contact us. (Calvin)
Hi Juergen,
Yes, I noted the same thing.
That's why I desire to use the unix awk in cygwin but after days of
trying connecting in with the windows native vim version, I gave up.
I tried also to use the gvim version in cygwin but that gave a lot of
troubles also and I'm new to unix.
Don't know anything about display, x-server, terminals, sudo, xhost.
Do you use only the gnu awk?
Regards,
Rameo
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment