Re: remote-silent and stdin
On 4/10/07, Mahesh Sivasubramanian [EMAIL PROTECTED] wrote: I am trying to do something to the effect of ls | gvim - --remote-client. or ls | gvim --remote-client - However, vi sees the - as a file name and opens a new filename. Is there way to open the stdin output on a gvim server? Do some of these do what you want : gvim --remote `ls` gvim --remote $(ls) gvim --remote-silent `ls` gvim --remote-silent $(ls) ? ... --remote-client Must be a typo. There is --remote and --remote-silent. There is no --remote-client. Yakov
Re: remote-silent and stdin
Mahesh Sivasubramanian/Lex/Lexmark 04/11/2007 10:57 AM To Yakov Lerner [EMAIL PROTECTED] cc vim@vim.org Subject Re: remote-silent and stdin Sorry I wasn't clear last time. I am trying to redirect the output of stdin to a remote client(not necessarily ls). Like if I want to do a cat file | gvim --remote-silent . Its looks like -remote-silent takes in only files as arguments. Mahesh Yakov Lerner [EMAIL PROTECTED] 04/11/2007 10:52 AM To Mahesh Sivasubramanian [EMAIL PROTECTED] cc vim@vim.org Subject Re: remote-silent and stdin On 4/10/07, Mahesh Sivasubramanian [EMAIL PROTECTED] wrote: I am trying to do something to the effect of ls | gvim - --remote-client. or ls | gvim --remote-client - However, vi sees the - as a file name and opens a new filename. Is there way to open the stdin output on a gvim server? Do some of these do what you want : gvim --remote `ls` gvim --remote $(ls) gvim --remote-silent `ls` gvim --remote-silent $(ls) ? ... --remote-client Must be a typo. There is --remote and --remote-silent. There is no --remote-client. Yakov
Re: remote-silent and stdin
[EMAIL PROTECTED] wrote:
Mahesh Sivasubramanian/Lex/Lexmark
04/11/2007 10:57 AM
To
Yakov Lerner [EMAIL PROTECTED]
cc
vim@vim.org
Subject
Re: remote-silent and stdin
Sorry I wasn't clear last time. I am trying to redirect the output of
stdin to a remote client(not necessarily ls). Like if I want to do a
cat file | gvim --remote-silent .
Its looks like -remote-silent takes in only files as arguments.
And its documented, too:
--remote [+{cmd}] {file} ...*--remote*
Open the file list in a remote Vim. When
there is no Vim server, execute locally.
There is one optional init command: +{cmd}.
This must be an Ex command that can be
followed by |.
The rest of the command line is taken as the
file list. Thus any non-file arguments must
come before this.
You cannot edit stdin this way |--|.
The remote Vim is raised. If you don't want
this use
vim --remote-send C-\C-N:n filenameCR
--remote-silent [+{cmd}] {file} ...*--remote-silent*
As above, but don't complain if there is no
server and the file is edited locally.
Note the line that says You cannot edit stdin this way.
Regards,
Chip Campbell
