On Wed, 2006-05-03 at 08:20 -0300, BG - Ben Armstrong wrote:
Uh-oh. OK, I see now the "-" which I hadn't noticed before. So this clearly doesn't work. I'll have to play with it some more to come up with a correct workaround, as mine only seems to work by accident.
This is unspeakably horrible:
cream --remote-silent "+call Cream_close()|call Cream_file_open(\"/path/file\")<CR>" "~/.cream_nofile"
This temporarily creates a buffer for ~/.cream_nofile (using Vim's open, not Cream's) and then Cream promptly closes it, opening the file we really want instead.
It seems the new vim uses inputsave() before opening (using "drop") the filename(s) passed to --remote. Thus, no matter what I do to try to hack around that filename, Vim always restores the input afterwards, defeating my attempts to do without an input file.
I'm quite discouraged.