Francesco Potorti` <[EMAIL PROTECTED]> writes:
> Well, maybe you gave me the right idea:
> give the message as standard input to
> ci -m "`cat`"
> I hope I understood what the issue is.
Currently, vc.el calls vc-do-command in lots of places. The standard
definition of vc-do-command uses call-process to do its thing, so it
only works locally. rcp.el provides its own version of vc-do-command
which uses shell-command and thus works remotely, as well.
Your suggestion would mean that I'd have to change vc.el to modify how
ci is being invoked. And this would only be a solution for ci, and it
breaks down as soon as we see a program which needs _two_ multi-line
arguments.
And besides, under csh your suggestion doesn't do what is wanted:
,-----
| $ csh
| % echo "`cat`"
| a
| b
| a b
`-----
Note how the last line shows that the newline in the input is
transformed into a space in the output.
Using sh, something even stranger happens:
,-----
| $ sh
| \$ echo "`cat`"
| a
| b
| aD
| b
`-----
Note the strange `D'. Both of the above were on a FreeBSD system.
I think what is _really_ needed is some mechanism which quotes
shell meta characters, and this mechanism either needs to find out
which shell its output is supposed to be used for, or it needs to use
a mechanism which works for all shells.
kai
--
A preposition is not a good thing to end a sentence with.
